This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Varargs macros subtly broken
- To: Jamie Lokier <egcs at tantalophile dot demon dot co dot uk>
- Subject: Re: Varargs macros subtly broken
- From: Neil Booth <NeilB at earthling dot net>
- Date: Wed, 27 Sep 2000 07:16:31 +0100
- Cc: Zack Weinberg <zackw at Stanford dot EDU>, gcc at gcc dot gnu dot org,gcc-bugs at gcc dot gnu dot org
- References: <E13dHl8-0005rl-00@kings-cross.london.uk.eu.org> <20000924225710.A12825@pcep-jamie.cern.ch> <20000924171436.F28755@wolery.stanford.edu> <20000925184254.A14482@pcep-jamie.cern.ch> <20000925224320.J6182@wolery.stanford.edu> <20000926125627.B17752@pcep-jamie.cern.ch> <20000926232108.A15334@daikokuya.demon.co.uk> <20000927014103.A20431@pcep-jamie.cern.ch>
Jamie Lokier wrote:-
> *boggle* you mean this is broken even without varargs? Ouch!
No, only in the varargs case.
> Lots of my programs use function-like macros in this way, for the most
> basic things like hash tables and sorting functions.
> E.g. "FAST_MERGE_SORT (a, b, STRCMP_LIKE_COMPARISON_MACRO)".
>
> I'll have to see if they still compile. Oh, they do. What am I missing
> from the above explanation?
Just that the normal case is taken care of <g>.
Neil.