Akim Demaille wrote: > In the case of stack.hh, I think we don't care. In fact, I expect > people to '%define api.stack.file none' to not generate this file.
BTW, couldn't this be the default, since you say it's not needed outside of the parser? Would it break anything? > But in the case of location.hh/position.hh, it might be important > to generate them in foo/ast while the parser is in foo/parse. > But then, what should the #include look like? Maybe we cannot > just invent it, and should also introduce api.stack.include to > specify it. > > Just thinking aloud. But I'd be happy to not be alone doing so :) Maybe just leave it up to the user to give the necessary "-I" options then? > PS/ Not sure api.* is the appropriate prefix for file names. Maybe fhs.*? But I admit I haven't spent much thought on the symbol hierarchy in general. Regards, Frank
