Alan Manuel Gloria > ... and by my understanding, this should yield an error: > > . n(expr) n(expr 2) > > However there's no error signalled explicitly at this stage, and > although ANTLR might handle this correctly, I'm not so certain that a > naive Scheme translation would.
I've added an explicit "error" branch in the BNF for the "2 expressions after PERIOD" cases, so that it's "obvious". I've also tweaked the BNF so indented comments inside restart lists are clearly skipped. I've also added pre/post conditions. The *key* pre/post conditions are the state of the input stream (of the given port), so that's what I wrote about. E.G., t_expr's precondition is "At beginning of line". Take a peek at the "develop" branch's "sweet.g". --- David A. Wheeler ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Readable-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/readable-discuss
