|
From: | Hans Aberg |
Subject: | Re: warn about conflicting skeleton-generated files |
Date: | Wed, 13 Dec 2006 15:41:16 +0100 |
On 13 Dec 2006, at 09:41, Joel E. Denny wrote:
I think it would be useful if Bison were to recognize three forms of skeleton paths: 1. "/root/path" 2. "./cwd/path" 3. "path/relative/to/install"How about if we use C's method for resolving #include <...> instead?Are you proposing forms like following? // Bison install directory. %skeleton <yacc.c> // Current working directory. %skeleton "yacc.c" What about --skeleton?
Perhaps --skeleton=<yacc.c> --skeleton="yacc.c" possibly with the option of simplifying one of the forms to --skeleton=yacc.cThe situation I encounter, is that I write my own skeleton file, and want to include it in the project. In such a situation, one should be able to indicate the position of the skeleton file relative the directory where Bison is invoked (typically where the 'make' file is).
Hans Aberg
[Prev in Thread] | Current Thread | [Next in Thread] |