Alan Manuel Gloria: > A precis: the tokenizer is not a separate pass, but rather implemented > as a stateful procedure that will consume exactly one token on the > input stream...
Can you start by focusing on the preprocessor/tokenizer for the existing BNF? You're absolutely right that the current material leaves that to text (as did SRFI-49, to be fair), and making it more formal is likely to be an improvement. > If it finds a "<code>!</code>" character after > the indent, > emit INITIAL_INDENT_WITH_BANG > and end processing. Hm, I pull in all the indent chars, and then check for "!". That way, multiple bad "!" will only be complained about once. I found that processing SAME was actually more of a pain, and not really helpful, but your mileage may vary :-). I plan to implement most of the indent/dedent stuff by using comment_eol to grab and return the indent string, and then use string comparisons to determine the difference. That's how the current one works, so I know it works well. --- 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 Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
