[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --no-parser options
From: |
tim |
Subject: |
Re: --no-parser options |
Date: |
Sat, 04 Aug 2007 12:46:43 +1000 |
On Fri, 2007-08-03 at 22:18 -0400, Joel E. Denny wrote:
> On Wed, 1 Aug 2007, tim wrote:
>
> > My suggestion is that until the option is fixed
> >
> > a) The option produce a warning that it's ignored
> > b) The documentation should reflect that it doesn't work.
>
> It looks like that's been broken for a long time. Did it ever work? Do
> we need it? Maybe Paul Eggert or Akim Demaille can comment.
>
--no-parser would be quite useful to me. I want to use the parse tables
in a lisp program. The less C code I have to filter out the better.
> > My suggestion is that
> > c) If skeleton name given includes "/" or "\" it is assumed to be the
> > full pathname, otherwise it is assumed to be in the default directory.
>
> This has already been implemented in CVS except it doesn't handle systems
> that use "\". Again, I would like to hear Paul's or Akim's advice on
> whether Bison should worry about that. I note that, even prior to this
> %skeleton change, Bison's output_skeleton function in src/output.c assumed
> that Bison's installation directory used only "/" as a directory
> delimiter.
That's good - I'll start using the CVS version.
Tim Josling
- --no-parser options, tim, 2007/08/01
- Re: --no-parser options, Joel E. Denny, 2007/08/03
- Re: --no-parser options,
tim <=
- Re: --no-parser options, Joel E. Denny, 2007/08/04
- Re: --no-parser options, tim, 2007/08/05
- Re: --no-parser options, Joel E. Denny, 2007/08/05
- Re: --no-parser options, Satya, 2007/08/06
- Re: --no-parser options, Hans Aberg, 2007/08/07
- Re: --no-parser options, Joel E. Denny, 2007/08/11
- Re: --no-parser options, Hans Aberg, 2007/08/12
- Re: --no-parser options, Joel E. Denny, 2007/08/11
- Re: --no-parser options, Hans Aberg, 2007/08/05
- Re: --no-parser options, tim, 2007/08/06