> Le 5 août 2014 à 13:47, Maxim Filipenko <mfilipe...@yandex.ru> a écrit : > > Hi all! > > If I specify "%define parse.trace" or -t option to bison with explicit > relative path to glr.c skeleton with -S option or "%skeleton > relative_path_to_local_file" directive, I get error "%define variable > 'parse.trace' is not used". If I specify glr.c from installation directory > (just "glr.c"), then error is missing. Without trace options in both cases > (relative path and installation directory) parser generates the same .cc > file.
Hi Maxim, You are right, the code often checks the skeleton name to decide what's to be done. We could add calls to basename to avoid the dependency on the directory name, yet that would mean we can no longer tell the difference between glr.c from Bison itself, and something that would be customized by the user. I suppose the clashes between user skeletons and Bison skeletons are unlikely, or precisely on purpose, in which case we could decide to use basename, indeed. WDYT?
