Yes, definitely. There is only one version of quex on my machine, and if you'll look at build.sh script in package that I uploaded earlier you will find that QUEX_PATH is there, explicitly exported and set to where quex is installed - I think it points exactly where it should. I will try to install newest Debian or Ubuntu, update all Python packages and try to build it - I think outdated Python can be a reason for failure - I don't know why and how, but this is the only thing I really haven't tr...
Well, I could reproduce it each time, so probably this is something in my environment. I use Debian 9.11, and have two version of python: 2.7.13 and 3.5.3. If this doesn't help, then I think this bug can be pretty safely ignored - I already moved away from --fes switch and if nobody else experiences this problem then maybe it is some peculiar part of my build environment - though I have to admit that I had it on two older Debian versions and currently have on two separate environments - but they...
Yes, exactly this file. Sorry that it took to long to respond, I don't know why I did not receive email with notification about your question.
Yes, original bug was with 0.69.4, but later example was compiled with 0.70.0. Have you tried generating lexer from attached files? I no longer use --fes option, but aforementioned example definitely displayed described behaviour.
"ISO C++17 does not allow `register` storage class specifier" warning
Hi, were you able to look at this?
Hello, were you maybe able to look at this? Sorry again for giving feedback after so much time, but I really were unable to do it earlier.
Sorry for taking THREE MONTHS to answer, but I had to take a great detour. Attached file quex-fes-error.txz is a full example of what goes wrong. You can build this example by running build.sh scipt available in the archive. You should probably change CXX and CC to something sensible, I compiled g++-9.2.0 myself and use it extensively. I compiled on Debian and have quex installed from 0.70 deb.
Unfortunately same thing happens after installing 0.70.0. I'll veryfiy everything once again and prepare sources to reproduce this issue. Sadly I can't prioritize it as I can live without --fes option, but it would be nice to have consistent file naming scheme.
It seems that generator breaks down if --fes option is used. Without it everything (after required changes) everything works as expected. But it means that --fes option is probably broken.
Quex generates header that includes itself without guard