> you know how main() can be declared with varying parameter counts,
> like
>
> int main()
>
> or
>
> int main( int argc, const char* argv* )
>
> and even more. Does this work for any function? If I pass a function
> more parameters than it actually uses, is that safe with OS X's
> current Mach-O ABIs?
Last I knew, that was a part of the C language standard.
If you use the elipsis (...) it might even compile :-).
open, on Darwin/Mac OS X, employs this so it can accept variable
arguments after the required ones. see /usr/src/sys/fcntl.h around
line 393.
And it works too. Lots of Unix APIs depends on that. Off the top of my
head, the third argument of open() is optional and signal handers were
originally defined to take one argument, but now they take three. Old
handlers will obviously work, since they ignore the second and third
arguments.
Same with libc. Think "printf" :-)
Cheers,
davez
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
