Re: warn about conflicting skeleton-generated files

[Paul Eggert]

"Joel E. Denny" <address@hidden> writes:

> So, here's my original proposal again:
>
>   1. "/root/path"
>   2. "./cwd/path"
>   3. "path/relative/to/install"
>
> Your proposal agrees with #1 and #3 and adds --skeleton-path to influence 
> #3.
>
> Would it hurt to also support #2?

#2 bothers me because it's a special case of #3 but with a different
interpretation from #3.

How about if the default skeleton path is the directory the grammar
was found in, followed by the standard Bison skeleton directory?
That's similar to how '#include "foo.h"' works in C.  A downside of
this approach is that one cannot refer to the standard Bison skeleton
file if there's a file with the same name in the working directory,
but the usual solution for this (#include_next in GCC) is even better
than #2 since it works even in include files and even when the include
path length is longer than 1.