Re: warn about conflicting skeleton-generated files

[Joel E. Denny]

On Wed, 13 Dec 2006, Paul Eggert wrote:

> I don't see the need for both "" and <> forms.  I was thinking more
> about how cc -I works.  That is, Bison could have a default internal
> path that it uses to look up file names, and the user could override
> this path on the command line.  (Sorry, I don't have a concrete
> proposal.)
> 
> > What about --skeleton?
> 
> I assume the simplest would be if --skeleton uses the same path that
> %skeleton does.

So, you're thinking that something like:

  bison --skeleton-path=.

would tell Bison to look for the skeleton file (declared with either 
%skeleton or --skeleton) in the current directory?

Potentially, the user could specify multiple directories with 
--skeleton-path such that earlier directories (should they contain the 
specified skeleton file) have precedence over later ones.  However, this 
seems like more complexity and potential confusion than we really need.

Aside from that, your proposal just seems like a more verbose version of 
mine.  To be fair, I'll assume -P is an abbreviation for --skeleton-path. 
Now:

  bison -P /some/path -S skel.c

versus:

  bison -S /some/path/skel.c

Or:

  %skeleton "skel.c"

  bison -P /some/path

versus:

  %skeleton "/some/path/skel.c"

By the way, if we go with my proposal, I think yours could easily be added 
later without conflict.