README.txt in rubylexer-0.7.0 vs README.txt in rubylexer-0.7.1

@@ -65,27 +65,22 @@
   ?   can be start of character constant or ternary operator
   `   can be method name or start of exec string
   any overrideable operator and most keywords can also be method names
 
 == todo
-test w/ more code (rubygems, rpa, obfuscated ruby contest, rubicon, others?)
-these 5 should be my standard test suite: p.rb, (matz') test.rb, tk.rb, obfuscated ruby contest, rubicon
 test more ways: cvt source to dos or mac fmt before testing
-test more ways: run unit tests after passing thru rubylexer (0.7)
 test more ways: test require'd, load'd, or eval'd code as well (0.7)
 lex code a line (or chunk) at a time and save state for next line (irb wants this) (0.8)
 incremental lexing (ides want this (for performance))
 put everything in a namespace
 integrate w/ other tools...
 html colorized output?
 move more state onto @parsestack (ongoing)
-the new cases in p.rb now compile, but won't run
 expand on test documentation
 use want_op_name more
 return result as a half-parsed tree (with parentheses and the like matched)
 emit advisory tokens when see beginword, then (or equivalent), or end... what else does florian want?
-strings are still slow
 emit advisory tokens when local var defined/goes out of scope (or hidden/unhidden?)
 token pruning in dumptokens...
 
 == known issues: (and planned fix release)
 context not really preserved when entering or leaving string inclusions. this causes
@@ -94,10 +89,12 @@
 string tokenization sometimes a little different from ruby around newlines
   (htree/template.rb) (0.8)
 string contents might not be correctly translated in a few cases (0.8?)
 symbols which contain string interpolations are flattened into one token. eg :"foo#{bar}" (0.8)
 '\r' whitespace sometimes seen in dos-formatted output.. shouldn't be (eg pre.rb) (0.7)
-windows or mac newline in source are likely to cause problems in obscure cases (need test case)
+windows newline in source is likely to cause problems in obscure cases (need test case)
 unterminated =begin is not an error (0.8)
 ruby 1.9 completely unsupported (0.9)
 character sets other than ascii are not supported at all (1.0)
-
+regression test currently shows 14 errors with differences in exact token ordering
+-around string inclusions. these errors are much less serious than they seem.
+offset of AssignmentRhsListEndToken appears to be off by 1