> However, I'm not sure if it's worth the effort as I myself rarely use
> matchg function,

I agree that matchg is probably not worth trying to support with a 
separate syntax.

I was thinking of
var["regexp"]
as a shortform for
regex.match(var, "regexp", ?"\0", "temp_var")
where the expression returns the result that regex puts in temp_var 
(and PowerPro would take care of handling the temp_var internally); so 
you could say thinks like
if (filepath["some regexp"]) do
 statements to handle file paths matching
endif

Also
var["regexp"] = "string"
for
regex.replace(var, "regexp", "string","var")

In both cases, the regex integer return code would be placed in a 
global variable _REGEX_

I don't use regular expressions much, but one problem with above is 
there is no way to do replaceg, which I imagine would be a big hole.

Right now, I cannot think of a clean way to do global replace (by 
clean, I mean avoiding adding some new PowerPro syntax characters).  
Any ideas?

Another totally different approach would be to copy the Python syntax 
using compiled re's, which should be possible as well, based on a 
brief look.   Any preferences?  









------------------------ Yahoo! Groups Sponsor --------------------~--> 
Home is just a click away.  Make Yahoo! your home page now.
http://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/JV_rlB/TM
--------------------------------------------------------------------~-> 

Attention: PowerPro's Web site has moved: http://www.ppro.org 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/power-pro/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to