Closed GoogleCodeExporter closed 8 years ago
Well, the contents of a namespace block are actually at toplevel syntactically,
which requires a semicolon to terminate declarations and definitions, so it
makes sense to have them here, too.
There's also a technical issue, namely that the grammar causes all kinds of
nasty LALR parsing conflicts if I allow to drop the final semicolon in a
namespace block. IIRC, that's due to the way declarations are parsed which
requires some lexical tie-ins so that operator declarations can be parsed
correctly. I didn't deem this important enough to rewrite the entire grammar
(and possibly the lexer) for it.
I still don't consider this a big issue, so I'm closing this bug for now. If
you consider it important, you're invited to reopen it -- preferably with the
appropriate patches to parser.yy and lexer.ll to make it work. ;-)
Original comment by aggraef@gmail.com
on 14 Jun 2012 at 6:22
No, not important. If there are technical reasons as you describe I'd also say
leave it be. I just pointed it out in case it was a simple oversight. Thanks.
Original comment by dubious...@gmail.com
on 14 Jun 2012 at 3:01
Original issue reported on code.google.com by
dubious...@gmail.com
on 14 Jun 2012 at 12:54