UVviewsoft forums

Thanks!. That was the problem.

I'm afraid it doesn't work either.

^[\x20\x09]*\*.*
does not match the comment in line 7 nor the comment in 5...

I get that \s matches newline but even so, I don't see why my regexp shouldn't work.

I have a problem with this regexp: ^\s*\*.* I'm trying to tag as a comment any line in which the first non whitespace is an asterisk. But as can be seen in the image, even when the comments in line 3 and 5 are matched (they appear in green), the comment in line 7 is not. And the only difference betw...

\:[a-z]+\: Name cannot have 1..9? If you mean in 'Database' parser, maybe it can. I haven't found any information regarding which characters are allowed there so we are using only alpha. [a-z_0-9]+ same as \w+ Ok. close?\s+proc.* better at end "\w*" , not .* (. is any) It can be any chara...

Alexey wrote:note: (next update). Add name to NOTES tab of lexr. Not to lexer name (dbase.3.senen)
>>>Author: senen (email@)

That was only to distinguish your lexer from mine while doing my tests. I didn't intend to distribute that...

I've updated the lexer with your suggestions. Thank you for them. I've seen that instead of reusing the EndClass rule to close the Procedures (as I had tried first) you have defined a new EndClass-2 rule to do that. I've renamed that rule to EndProcedure, to better reflect its role. Beside that, I'v...

Here you have the exported lexer and a dummy source example. In your lexer you are using ENDCLASS to detect the end of a procedure, but that doesn't always work, because procedures can be outside classes. I've tried something similar that I thought could work, that is: using the 'EndClass' rule in m...

I'm still having some problems defining the lexer for Visual dBase. Let's supose I have this code CLASS Class1 Procedure P1 some code Procedure P2 some code ENDCLASS CLASS Class2 some code ENDCLASS "CLASS" and "ENDCLASS" have respectively a "Range start" and "Range...

2--list all keywords with short+long view. so list "procedure" and "proc"--also for rules, for folding, and for hilite. Ok. I was thinking that I would need all the intermediate versions: "procedure", "procedur", "procedu",... "proc", but ...

1--yes, possible. Make 2 rules for procedure. 1st takes "set procedure to", 2nd takes only "procedure", and SET "skip next rules" for rule1 so rule2 won't work if rule1 worked. (rule1 must have 3 tokens: set, procedure, to... don't use regex for whole line) Thank you. ...