Re: Segmentation fault using lalr1.cc

[Paul Eggert]

Tim Van Holder <address@hidden> writes:

> This is because lalr1.cc also has '#include @output_header_name@'.
> With that wrapped in an m4_if as well, bison no longer crashes.

Thanks; I'll send a proposed patch to bison-patches and will cc: to you.

> I don't see why bison couldn't/shouldn't warn "Skeleton uses
> @output_header_name@ which is only available if the -d option is
> given" (or something similar).

Good suggestion.

> BTW, 'bison -S lalr1.cc foo.y' still produces a .c file; this seems a
> bit odd.

Yes, it seems odd to me too.  But I don't use C++ so I am not
well-qualified to judge about Bison's handling (or mishandling) of
C++.