[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison 1.30f
From: |
Paul Eggert |
Subject: |
Re: Bison 1.30f |
Date: |
Wed, 12 Dec 2001 18:16:02 -0800 (PST) |
> Date: Wed, 12 Dec 2001 23:55:29 +0100
> From: Hans Aberg <address@hidden>
> >> #include <stdio.h>
> >
> >I agree that this shouldn't be in the output, as <stdio.h> intrudes on
> >the user's namespace. This is true for both C and C++.
>
> If this is C99 and C99 has namespaces, I wouldn't know (I haven't gotten
> this standard yet).
As I mentioned earlier, C99 doesn't have C++'s namespaces, but it does
have the traditional name spaces, which is what I was referring to.
> >As far as I know, <alloca.h> does infringe on the user name space in
> >all cases where <alloca.h> is actually included here. Do you know of
> >a counterexample?
>
> It didn't look like that on mine (MacOS pre-X and old CodeWarrior
> compiler), but I do not know what happens with size_t: alloca is macroed to
> __alloca, which is a MacOS secret library function.
That infringes on the traditional name space, then, since it reserves
"alloca".
It sounds like we're converging.
- Bison & C++, (continued)
- Re: Bison 1.30f, Mike Castle, 2001/12/12
- Re: Bison 1.30f, Akim Demaille, 2001/12/13
- Re: Bison 1.30f, Paul Eggert, 2001/12/10
- Re: Bison 1.30f, Hans Aberg, 2001/12/11
- Re: Bison 1.30f, Hans Aberg, 2001/12/11
- Re: Bison 1.30f, Paul Eggert, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/12
- Re: Bison 1.30f,
Paul Eggert <=
- Re: Bison 1.30f, Hans Aberg, 2001/12/11
- Re: Bison 1.30f, Akim Demaille, 2001/12/12
- Re: Bison 1.30f, Akim Demaille, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/12
- Re: Bison 1.30f, Paul Eggert, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/12
- Re: Bison 1.30f, Paul Eggert, 2001/12/12
- Re: Bison 1.30f, Hans Aberg, 2001/12/13
- Re: Bison 1.30f, Akim Demaille, 2001/12/13
- Re: Bison 1.30f, Hans Aberg, 2001/12/13