1

Closed

"in-progress" strings (ie those with no closing quote) aren't parsed as string tokens

description

Currently, the boo lexer will barf and throw an exception (which we supress) in the case of encounting a malformed string token, like this:

def SomeMethod():
print "This is a malformed string

the classic case for this occuring: in the process is creating a string literal, you haven't yet entered the closing quote...

So until you enter the closing quote, the string is treated as a group of whatever items are there (ie identifiers, operators, etc)... this is not the default behavior for other languages in the IDE, and isn't desired behavior.
Closed Aug 29, 2008 at 5:35 PM by
fixed with peg-based synytax highlighting

comments

olsonjeffery wrote May 29, 2008 at 12:54 AM

tenative fix stored in my "syntax_cleanup" branch.. this is also where I will work on re-implementing parsing comments or varying sorts.

I'm gonna try to be more "responsible", ie not merging my in-progress stuff into master. no brainer, i guess.

olsonjeffery wrote Jun 1, 2008 at 5:31 PM

i've found some edge cases where this breaks down, ie:

foo = "bar" +"baz

in this case, "baz" won't parse and be colorized as a string token (in progress) because it doesn't have the whitespace padding.. still fiddling with this in syntax_cleanup