[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: warn about conflicting skeleton-generated files
From: |
Joel E. Denny |
Subject: |
Re: warn about conflicting skeleton-generated files |
Date: |
Wed, 13 Dec 2006 03:41:44 -0500 (EST) |
On Tue, 12 Dec 2006, Paul Eggert wrote:
> "Joel E. Denny" <address@hidden> writes:
>
> > 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?
- warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/09
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/10
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/12
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files,
Joel E. Denny <=
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/13
- Re: warn about conflicting skeleton-generated files, Paul Eggert, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Joel E. Denny, 2006/12/14
- Re: warn about conflicting skeleton-generated files, Hans Aberg, 2006/12/14