Re: warn about conflicting skeleton-generated files

[Hans Aberg]

On 10 Dec 2006, at 01:16, Joel E. Denny wrote:

> Bison should warn about:
>
>   bison --skeleton="lalr1.cc" --graph="location.hh" foo.y
>
> since lalr1.cc generates a location.hh.  I committed the following  
> to make
> that happen.

Another problem, somehwat irritating, is that Biosn does not know how  
to parse the filepaths of the skeleton files. So if I write my own,  
and put it in the project in the home directory, I need to write  
things like:
  bison --skeleton=../../../../Users/myself/Development/MLI/sources/ 
Parser/my_lalr1.cc
even if Bison is invoked form the last directory. So variations might  
be:
  bison --skeleton=~/Development/MLI/sources/Parser/my_lalr1.cc
  bison --skeleton=$HOME/Development/MLI/sources/Parser/my_lalr1.cc
  bison --skeleton=$PWD/my_lalr1.cc
  bison --skeleton=$BISON/../../../../Users/myself/Development/MLI/ 
sources/Parser/my_lalr1.cc
  bison --skeleton=/Users/myself/Development/MLI/sources/Parser/ 
my_lalr1.cc
In the last one, Bison would recognize that a filepath starting with  
"/" is an absolute one.

  Hans Aberg