[Top][All Lists]

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

Re: Bison 1.30f

From: Paul Eggert
Subject: Re: Bison 1.30f
Date: Tue, 18 Dec 2001 18:00:21 -0800 (PST)

> Date: Tue, 18 Dec 2001 08:26:27 +0100
> From: Hans Aberg <address@hidden>

> I do not see how you infer that the Yacc program must start the
> names in the generated parser with yy or YY

I think we're going around in circles here, but to repeat the argument:

A conforming program (in the .y file) can use whatever names it likes,
  other than names beginning with yy or YY.
Yacc must support such programs.
To support those programs, yacc-generated names must be distinct from
  user names.
Hence yacc must generate only names starting with yy or YY.

> or that names be visible to the preprocessor;

But all the names we're talking about are visible to the preprocessor.

> to me, it says that other programs
> should not use them as the Yacc program may use them.

That's another way of saying the same thing.

> Also, C++ isn't (I take it) part of POSIX, so whatever POSIX says
> about macros under C, it is not valid under C++.

True, but C++ is similar to C, and has similar problems with
preprocessor names.  All other things being equal, it's simpler for
both users and maintainers if we treat the languages similarly.

reply via email to

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