> On 13 Mar 2018, at 23:23, Frank Heckenbach <[email protected]> wrote: > >> Bison 3.0.4 marks the constructor for the syntax_error class as 'inline' >> when generating a C++ scanner, which results in undefined references when >> the exception is thrown from a separate scanner file. Since this is the >> stated purpose of the syntax_error class (see >> http://lists.gnu.org/archive/html/help-bison/2013-07/msg00010.html), this >> appears to be a bug. > > Anyway, do you use the "--defines" option or "%defines" setting to > generate a header that you include in your other source files? If > so, AFAICS, the inline constructor is generated in the same header, > so it should be available in your other source file, too.
It ends up in the .cc file even with %defines, it seems. But it should properly be in the header file, and probably the other inlines too.
