Dan Sugalski <[EMAIL PROTECTED]> writes: > C's vararg handling sucks in many sublime and profound ways. It does, > though, work. If we declare in advance that all C-visible perl functions > have an official parameter list of (...), then we can make it work. The > calling program would just fetch function pointers from us somehow, and > do the call in. Can't. ISO C requires that all variadic functions take at least one named parameter. The best you can do is something like (void *, ...). -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
- Re: RFC 334 (v1) I'm {STILL} trying to understand this..... John van V
- Re: RFC 334 (v1) I'm {STILL} trying to understand t... Dan Sugalski
- Re: RFC 334 (v1) I'm {STILL} trying to understa... Simon Cozens
- Re: RFC 334 (v1) I'm {STILL} trying to unde... Dan Sugalski
- Re: RFC 334 (v1) I'm {STILL} trying to ... Russ Allbery
- Re: RFC 334 (v1) I'm {STILL} tryin... Simon Cozens
- Re: RFC 334 (v1) I'm {STILL} t... Dan Sugalski
- Re: RFC 334 (v1) I'm {STIL... John Porter
- Re: RFC 334 (v1) I'm {STIL... Jarkko Hietaniemi
- Re: RFC 334 (v1) I'm {STIL... John Porter
- Re: RFC 334 (v1) I'm {STIL... Dan Sugalski
- Re: RFC 334 (v1) I'm {STILL} tryin... Nicholas Clark
- Re: RFC 334 (v1) I'm {STILL} t... Dan Sugalski
- Re: RFC 334 (v1) I'm {STILL} trying to ... David L. Nicol
- Perl's parser and lexer will likely be in Perl ... Bradley M. Kuhn