tcl parser changes
Rene Zaumseil <[email protected]> Fri, 18 Nov 2011 21:01:40 +0100
| Newsgroups | gmane.text.doxygen.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, with the attached patch the tcl parser detects now correctly the following cases: Commands starting with \ (backslash) Command definitions followed with any whitespace before end of line. Regards rene PS. Is this the preferred way to send patches? ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Doxygen-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/doxygen-develop
diff_tclscanner.l.785_tclscanner.l
(text/plain, 339 B)
972c972
< <COMMAND>\x1A {
---
> <COMMAND>{ws}*\x1A {
976c976
< tcl.line_body1=yylineno-1;
---
> tcl.line_body1=yylineno;
979c979,986
< <COMMAND>{ws}*[;\n] {
---
> <COMMAND>{ws}*; {
> D
> tcl.string_commentcodify = "";
> tcl.string_commentline = "";
> tcl.line_body1=yylineno;
> tcl_command(-1,yytext);
> }
> <COMMAND>{ws}*\n {