Revised sal_fun string

1 view
Skip to first unread message

John Kopp

unread,
Apr 29, 2009, 9:56:23 PM4/29/09
to sem...@googlegroups.com
string sal_fun[] =
"^[ \t]@{{menu{bar}@}|{{data}|{help}|{key}def}"
+ "|{{public[ \t]#}?{{integer}|{string}[ \t]#}?proc}"
+ "[ \t]+}[a-zA-Z_]"

Adds menubar, datadef, helpdef and keydef to the functions list,
allows spaces or tabs between the left margin and the text, and
allows tabs everywhere that a space was required.

John Kopp
Columbia, MD

Howard Kapustein

unread,
Apr 30, 2009, 3:31:41 PM4/30/09
to sem...@googlegroups.com
You know, once thing that's REALLY annoying...You can't paste that into the Compressed View... prompt.
 
That regex is 110 characters long.
Try to paste it into the CompressedView prompt and it stops @ the 100th char...
 
That's because TSE.UI restricts it
...
proc mCompressView(integer show_functions)
    string expression[100], options[12]
...
Sammy, how about bumping up expression's size whenever you get around to making the next patch?
Strings are capped at what, 255? That would be handy.
 
[No, I'd never want to key in a 200 char search string. But I would (and do) paste in something long...]
 
   - Howard

John Kopp

unread,
Apr 30, 2009, 4:48:01 PM4/30/09
to sem...@googlegroups.com
Howard Kapustein wrote:
> You know, one thing that's REALLY annoying...You can't paste
> that into the Compressed View... prompt.

Oops| I missed the fact that I had increased the size of
expression to 255. In 2001, I encountered a similar problem with
the variable s in FindPara, told Sammy, and he increased its size
to 255 characters. Before recent versions, the regex search engine
could not handle an expression of 110 characters. I don't know
what the limit actually is. I remember there was some discussion
regarding this, but I've forgotten all the details.

Anyway, the short answer is: In the function mCompressView(...),
change expression[100] to expression[255].

John Kopp

Reply all
Reply to author
Forward
0 new messages