Joel E. Denny wrote:
Well, if we document how the splitting is done, then I figure they can't
complain too much. I certainly don't want to see Bison parse complex C++
constructs. Let the C++ compiler catch those errors.
Wouldn't it be both easy and powerful to solve that namespace thing
using "%define"s?
What I have in mind is one %define each for begin and end of the
namespace, something like this:
%define "namespace_intro" "namespace Gnu { namespace Bison {"
%define "namespace_outro" "} }"
The default would be set to
%define "namespace_intro" "namespace <prefix> {"
%define "namespace_outro" "}"
If that's possible that would
* take namespace parsing off Bison's shoulders and
* be flexible at the same time.
What do you think?
Sebastian
_______________________________________________
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
