Re: header file guards conflict

[Hans Aberg]

On 21 May 2012, at 16:02, Akim Demaille wrote:

> Le 21 mai 2012 à 15:41, Hans Aberg a écrit :
> 
>> On 21 May 2012, at 11:34, Akim Demaille wrote:
>> 
>>>> Is there a better way to do it?
>>> 
>>> This is indeed a problem.  I'm sure what the best way to
>>> address this is.  In addition, in some cases, creating the
>>> files location.hh, stack.hh etc. is more troublesome than
>>> useful.
>> 
>> Perhaps add infixes 'loc', 'stk', etc., so that a parser with name <name> 
>> gets files
>> <name>.loc.h
>> <name>.stk.h
>> etc.
> 
> Actually I want to have stack.hh disapear (it does not
> need to be exposed).  It's a good idea though for the
> others, but since people want to be able to rename,
> it shall be more general.
> 
> position.hh does not need to exist either, it can live
> within location.hh.

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.

Hans