[Info-vax] System implementation languages, was: Re: RMS record metadata, was: Re: Re; Spiralog, RMS Journaling (was
VAXman- at SendSpamHere.ORG
VAXman- at SendSpamHere.ORG
Mon Jun 27 10:54:33 EDT 2016
In article <nkr8ic$l4l$1 at dont-email.me>, "Robert A. Brooks" <FIRST.LAST at vmssoftware.com> writes:
>On 6/27/2016 9:03 AM, VAXman- at SendSpamHere.ORG wrote:
>> lawrencedo99 at gmail.com writes:
>>> On Friday, June 24, 2016 at 6:40:38 AM UTC+12, David Froble wrote:
>>>
>>>> Sometimes some things just don't mix well. Not sure why I've had such a
>>>> problem with C. But I do. I'd have an easier time doing something in
>>>> Macro-32 than C.=20
>>>
>>> I can guess why this is the case. It=E2=80=99s because VMS system services =
>>> take so many arguments (e.g. 12 for $QIO, as I recall), so many of which ar=
>>> e often (mostly?) defaulted, that you really need the ability to pass argum=
>>> ents by keyword. Which you can do in MACRO, and in VAX PASCAL (what I used =
>>> to like to use, post-V1), but not in C.
>>
>> $QIO and other system services and VMS RTL utilities are easier in Macro because of
>> macros. If C had a decent macro, you wouldn't be complaining here now.
>
>The macro facility for BLISS is quite flexible as well.
;)
I didn't mention it because it was't previously mentioned. In some ways, it
is even better than Macro's.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
More information about the Info-vax
mailing list