Threaded Mode | Linear Mode

Tim Wessman · (This post was last modified: 10-15-2014 05:52 AM by Tim Wessman.)

This one is one of those deceptively simple ones.

Right now, it is a very simple checker and I agree it could use some more work. The problem really comes down to that the user's intentions are not clear in many cases when you are trying to match text mixed in with math. Is it matching forward/backwards in priority? Do you go backwards first? If so, how far. What if you go backwards until the first match (like in this case) but there is another better match? How about this case (cursor is at the |)?

2acos2asin(|tan)

Do you step backwards to asin and be done? Should you go back 4 and match, but then continue to go back more and find acos2asin? Why not move forward to tan and match that? It is closer and fewer characters away so why wouldn't tan be the correct one? Or should that whole thing be parsed as 2*acos(2)*asin(tan... ???

Right now, the logic is basically go backwards skipping over ( until it finds a match or hits an invalid name character. If it didn't find anything, move forward to see if there is another match in front of the cursor.