#2 Reserved names

[David Blaikie]

A request for enhancement. If a fixed set of names were
reserved for the implementation code in the emitted
BURM then it would avoid potential conflicts with names
used for user defined properties. (I'm thinking of
something along the lines of the
implementation-reserved names (leading underscore
followed by uppercase, and any double underscore) in
C++, but other schemes could be adopted).

[Tom Harwood]

Logged In: YES
user_id=557260

See bug #1145481, which describes the work necessary to get
JBurg's ANTLR-like #var substitution working correctly. A
JBurg grammar with good #var semantics could set a directive
that disabled all implicit variable passing.

[Tom Harwood]

Logged In: YES
user_id=557260
Originator: NO

On further consideration, I think this idea has merit independent of ANTLR-like #var semantics.

[Tom Harwood]

Java side of this is in and tested; C++ part tomorrow when I have a machine with an operational C++ setup.

[Tom Harwood]

Current behavior prefixes BURM-specific names with double underscore, could be modified to allow prefix by user specification on the command line or in the grammar.