1

Closed

Aberrations in multiline comment syntax highlighting

description

Currently, multiline comments in BooLangStudio parse, but has some issues. Specifically, if there are opening/closing quotes embedded in the comments (single, double or tripple).

When this happens, the highlighter will "un-color" the space of and the space before where the quote character is at. If it's a triple-quote, it'll "un-color" three spaces before the triple-quote token, not to mention the triples themselves.

This is most likely something to do with how BooScanner is dealing with tokens that it receives back from the lexer in the ScanTokenAndProvideInfoAboutIt() method.
Closed Aug 29, 2008 at 4:34 PM by
fixed with new, Peg-based syntax highlighting. closed

comments

olsonjeffery wrote May 19, 2008 at 9:32 PM

made some changes, reflected in most recent revision of git repo for the project... it perhaps a "90-percent" solution. While typing triple-quotes.. it looks like it's still able to break colorizing.. but you close the triple-quote (enclose the string), then the aberration will go away.

Also, string that end in trailing "operator" tokens (ie anything that is not an identifier (so parens, commas, periods, asterisks, etc)... will NOT be colorized.

Also, if the line ends in a SINGLE identifier (that is, [0-9a-zA-Z]), that single identifier token will not be colorized. The token will become colorized if you add one or more characters to the token... so:

Foo("bar")a <-- trailing 'a' would not be colorized while the rest of the line would be
Foo("bar")ab <-- in this case, the trailing 'b' would be colorized..

curious.

olsonjeffery wrote May 27, 2008 at 10:25 PM

the boo deps have been reverted to the "vanilla" form.. so currently all comment colorizing is broken... I intend to handle these tokens in BooScanner.ScanTokenAndProvideInfoAboutIt()

more news as it develops.