LSL syntax highlighting bug

I found a small bug in the LSL editor last night and I can't seem to find any mention of it in the forums. It relates to putting a quote character in a string using the escape syntax (e.g. "\""

When you put that in a script it compiles and works as expected however the highlighting suggests the quotes are still open. Here's alittle script that shows the problem quite clearly...

(I'm actually at work atm so I don't have SL availble so this code is off the top of my head. Pretty simple though so I'd be surprised if there's any typos.)

default {
    state_entry() {
        llSay(0, "\"");
    }

    touch_start(integer num_detected) {
        llSay(0, "Touched!");
    }
}

What you should see when you put that into the LSL editor is that everything after the point where the "\"" appears will be in green. Except for the "Touched!" which will be black. Basically the string syntax highlighting has been reversed because there's an odd number of quotes. However, as I said it compiles correctly and when you run it you should see the object say ".

This came up becuase someone was using an if statement to try and test for a quote within another string. Probably not something that would happen very often, but very annoying when it does.

Has this ever been brought up before? Are Linden Labs aware of it?

Yeeeeh, everyone's pretty much aware of it, LL's never bothered to fix it. Maybe it's something they'll actually fix in this round of bug fixing?

I don't think it has been fixed yet, so I filed it into our bugzilla database. It won't be in 1.5.6 but it might be in 1.5.7.

WTB bugzilla logs

Tisk. Xylor reported that one ages ago. There's even a comment about it in the ever-popular XyText script. He adds a comment to the end of the like with the slashed quote with another quote in it.

This bug is fixed in the next patch =)

wee haw!!!

I reported this one about 6 months ago... annoying when you need to use "\"", but not a show stopper.

- Ace

The good thing about this bug is that when you use "\"", you're usually using another "\"" to end the quote, so the LSL editor gets its knickers untwisted.

- Ace

As a workaround until the next patch, you 'fix' the editor window's confusion by putting another \" in a comment. Like so:

llSay(0, "\"");
// \" (This comment fixes the syntax highlighting bug)

while on the topic could we get a copy of the lex file used by the LSL compiler? the old one is almost a year out of date. (can be found on your favorite wiki mirror)