Dave Korn wrote:
There was under varargs, which didn't require to pass a named argument to
va_start; it's only with stdargs that it would be impossible.
I suspect that this is the underlying reason for the code having developed
this way: sometimes the first variadic arg is the last named arg (stdargs),
sometimes it is the first arg _after_ the last named arg.
ah, yes, that explains the later comment
/* Handle stdargs. LAST_NAMED is a slight mis-nomer; it's also true
for the unnamed dummy argument following the last named argument.
See ABI silliness wrt strict_argument_naming and NAMED_ARG. So
we only want to do this when we get to the actual last named
argument, which will be the first time LAST_NAMED gets set. */
I was trying to work out what the 'unnamed dummy argument' was. As we
no longer support varargs, this can be excised.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
[EMAIL PROTECTED] :: http://www.planetfall.pwp.blueyonder.co.uk
