Xref: utzoo comp.lang.c:20902 comp.std.c:1541 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!mcvax!hp4nl!botter!star.cs.vu.nl!maart From: maart@cs.vu.nl (Maarten Litmaath) Newsgroups: comp.lang.c,comp.std.c Subject: type-redef's (was: va_list used in) Keywords: Wadda ya thinka that! Message-ID: <3020@solo1.cs.vu.nl> Date: 18 Aug 89 14:58:30 GMT References: <1140@midgard.Midgard.MN.ORG> <10720@smoke.BRL.MIL> <2095@dataio.Data-IO.COM> <10739@smoke.BRL.MIL> <13572@bloom-beacon.MIT.EDU> <10766@smoke.BRL.MIL> Organization: V.U. Informatica, Amsterdam, the Netherlands Lines: 25 gwyn@smoke.BRL.MIL (Doug Gwyn) writes: \In article <13572@bloom-beacon.MIT.EDU> scs@adam.pika.mit.edu (Steve Summit) writes: \... \> #ifndef _VA_LIST \> #define _VA_LIST \> typedef int *__va_list; \> #endif \... \since size_t is a typedef it must be protected by some sort of \one-time interlock. The pANS allows a preprocessor redefinition equal to the original definition: #define pipo aap #define pipo aap #define clown(x, y) monkey(y, x) #define clown(a, b) monkey(b, a) /* allowed? */ Why is a type-redef still forbidden? typedef foo bar; typedef foo bar; -- kilogram, n.: the amount of cocaine |Maarten Litmaath @ VU Amsterdam: you can buy for $100K. |maart@cs.vu.nl, mcvax!botter!maart