On Jan 15, 2022, at 03:57, Akim Demaille wrote: > I personally feel that generating these prototypes automatically is actually > more complex (for the user, not for Bison) than merely specifying them.
Ok. Can you provide any guidance for how to specify them? I am a maintainer of packages within the MacPorts package management system. I've encountered many of our ports that fail to build for this reason, and I haven't known how to fix them. For other implicit declaration of function problems it's usually been a simple matter of including a missing header or writing a function prototype, but with bison/flex, there isn't a .c or .h file into which such a prototype could be inserted, and even if I knew what file to insert it into, I wouldn't know what prototype to write.
