fighting the code

Why doesn’t automake/autoconf properly recognise the way to use Flex/Bison with C++ scanner/parser generation? I use a .ll file and it thinks the output is going to be a .c instead of a .cc. Likewise I use a .yy file and it screws up the includes in my bison output because it decides to go substituting into the mix…

Making wrong assumptions is the quickest way for software to show itself as the unintelligent thing that it is.

One Response to “fighting the code”

  1. sylvene says:

    Why? Maybe it's like fighting the Common Cold?


Leave a Reply