[Info-vax] C... the only winning move is not to play...

[VAXman- at SendSpamHere.ORG]

In article <1811ca16-8a90-4cb3-b155-e18b9786f051 at googlegroups.com>, Steven Schweda <sms.antinode at gmail.com> writes:
>> OK.  The function is STR$CONCAT.
>
>   At last.
>
>   I lost much interest in this thread when the first few
>messages failed to reveal what the actual problem was, so I
>may have missed something, but when I'm looking for
>compatibility with old systems and/or header files, I usually
>avoid defining __NEW_STARLET.  I'm currently too lazy to
>check a VAX at V7.x, but on my V8.3 Alpha system, that would
>seem to select a simplified (and less troublesome?)
>declaration of str$concat():
>
>#ifdef __NEW_STARLET
>unsigned int str$concat(
>        void *destination_string,
>        void *source_string_1,
>        __optional_params);
>#else   /* __OLD_STARLET */
>unsigned int str$concat(__unknown_params);
>#endif  /* #ifdef __NEW_STARLET */
>
>   I like the type checking, but if defining __NEW_STARLET
>kept me from getting the job done, then I might make it
>optional (or dependent on __DECC_VER or __CRTL_VER or
>something).

__NEW_STARLET fixed up many of the "typing" issues.  When it's defined, the
header's definitions more closely parallel documented argument definitions.
It's nowhere near perfect and there are still many too many (casts) needed
to make everything copacetic, but it's a start.  It would all have been in
Macro if it were up to me but the customer said they can only read C.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.