[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: --no-parser options

From: Joel E. Denny
Subject: Re: --no-parser options
Date: Fri, 3 Aug 2007 22:18:25 -0400 (EDT)

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.

> 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 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]