[Top][All Lists]

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

Re: filenaming with .yxx extensions

From: Paul Eggert
Subject: Re: filenaming with .yxx extensions
Date: Wed, 27 Feb 2002 05:53:57 -0800 (PST)

> From: Akim Demaille <address@hidden>
> Date: 27 Feb 2002 09:36:55 +0100

> bison --define=foo.z -o foo.x foo.y

This seems like it would be an adequate workaround for OpenOffice.org.
If they use this:

bison -d -o .../rscyacc.yxx --defines=.../rscyacc.yxx.h rscyac.y

it should work as they want, regardless of Bison version.

> Now, the question is:
>         bison foo.y -d -o foo.x
>            => error (my preferred)
>            => foo.x.c, foo.x.h
>            => foo.c, foo.x.h

An error is OK with me, assuming the user has not specified the
--defines=FILE option.

However, whatever solution is adopted, this should be documented
better.  When I looked under Bison invocation, it said:

       Specify the FILENAME for the parser file.

       The other output files' names are constructed from FILENAME as
       described under the `-v' and `-d' options.


       Pretend that `%defines' was specified, i.e., write an extra output
       file containing macro definitions for the token type names defined
       in the grammar and the semantic value type `YYSTYPE', as well as a
       few `extern' variable declarations.  *Note Decl Summary::.
       Same as above, but save in the file DEFINES-FILE.

so I still don't know how the file names are constructed.  This stuff
should all be explained clearly and concisely under -o.
(Documentation should be the first step, before you write any code.

reply via email to

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