[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: header file guards conflict
From: |
Hans Aberg |
Subject: |
Re: header file guards conflict |
Date: |
Mon, 21 May 2012 18:27:06 +0200 |
On 21 May 2012, at 18:17, Akim Demaille wrote:
> Le 21 mai 2012 à 17:55, Hans Aberg a écrit :
>
>> Is there any reason to not put all stuff that is public in the parser
>> header? This would eliminate the need for any additional header files.
>
> That's the plan for those that need not be public.
> location.hh is different: you may use it for your
> ASTs if you wish. I, for one, do that.
Hm, I meant: put all stuff that the user might access in the parser header, and
the other stuff in the parser source. The names belonging to different parsers
won't collide if given different namespaces.
Hans
Re: header file guards conflict, Wei Song, 2012/05/21
Re: header file guards conflict, Hans Aberg, 2012/05/21
- Re: header file guards conflict, Akim Demaille, 2012/05/21
- Re: header file guards conflict, Hans Aberg, 2012/05/21
- Re: header file guards conflict, Akim Demaille, 2012/05/21
- Re: header file guards conflict,
Hans Aberg <=
- Re: header file guards conflict, Akim Demaille, 2012/05/21
- Re: header file guards conflict, Hans Aberg, 2012/05/21