[Lxr-commits] CVS: lxr/lib/LXR/Lang ectags.conf.documentation,NONE,1.1 ectags.conf,1.3,1.4
Brought to you by:
ajlittoz
From: Dave B. <bro...@us...> - 2004-07-15 20:25:37
|
Update of /cvsroot/lxr/lxr/lib/LXR/Lang In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16883/lib/LXR/Lang Modified Files: ectags.conf Added Files: ectags.conf.documentation Log Message: pull out comments into a seperate file so ctags doesn't display warnings --- NEW FILE: ectags.conf.documentation --- AFAIK, there's know way to embed comments into ectags.conf VB regexps modified from http://www.rutherfurd.net/weblog/2003/04/ The two variable lines are a bad hack to match array variables but not match functions/subs We define SQL2 with regexps because the built-in SQL parsing doesn't work right Unfortunately this indexes supposed identifiers in comments so we have to make the regexps as restrictive as possible. Often we get invalid field matches because comments include datatype keywords like 'date', so the field regexp has an ugly hack that you can't have any words between the beginning of a line and the identifier before the datatype Index: ectags.conf =================================================================== RCS file: /cvsroot/lxr/lxr/lib/LXR/Lang/ectags.conf,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- ectags.conf 13 Jul 2004 13:35:48 -0000 1.3 +++ ectags.conf 15 Jul 2004 20:25:26 -0000 1.4 @@ -1,4 +1,3 @@ ---regex-comment= VB regexps modified from http://www.rutherfurd.net/weblog/2003/04/; the two variable lines are a bad hack to match array variables but not match functions/subs --langdef=VB --langmap=VB:.bas.cls.ctl.frm.vbs --regex-VB=/^[ \t]*(Public|Private|\b)[ \t]*Sub[ \t]+([a-zA-Z0-9_]+)/\2/s,subroutine/i @@ -11,7 +10,6 @@ --regex-VB=/^[ \t]*(Public|Private|\b)[ \t]*Enum[ \t]+([a-zA-Z0-9_]+)/\2/e,enum/i --regex-VB=/^([a-zA-Z_]+):/\1/l,label/i ---regex-comment= we define SQL2 with regexps because the built-in SQL parsing doesn't work right; unfortunately this indexes supposed identifiers in comments so we have to make the regexps as restrictive as possible. Often we get invalid field matches because comments include datatype keywords like 'date', so the field regexp has an ugly hack that you can't have any words between the beginning of a line and the identifier before the datatype --langdef=SQL2 --langmap=SQL2:.sql --regex-SQL2=/^[ \t]*CREATE[ \t]+([a-zA-Z0-9 \t]*)?TABLE[ \t]+([^.]+\.)?"?([a-zA-Z0-9_@.]+)/\3/t,table/i |