🚀 go-pugleaf

>Oh?  If this is aberrant coding, you might want to look at your
>varargs.h file whose operation relies on these assumptions; and this is
>in the ANSI proposal.

Sigh....   Varargs is DEFINED as being machine-dependent - in other words,
those varargs macros/functions may have to be rewritten for every machine -
it is up to the system providers to provide definitions that work for a
SINGLE machine:  the one that is being compiled for.  Any user code that
does this is not portable.

>>>	int a,b, *ptr;
>>>
>>>	ptr = &a;
>>>	ptr++;
>>>	/* ptr now points to b */

Any program that is expected to work on more than one machine MUST NOT
make assumptions about memory layout.  This is the reason why varargs
exists:  So that 100's of programs do not have to make such assumptions!
Sure, this is legal C, but the trailing comment is NOT NECESSARILY TRUE!