Onig's PERL syntax

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
Rex, do you have any docs which say whether Onig's PERL syntax honors the PERL quantifier {m,n} (at least m, at most n)?

AFAICT, with your @REGEX and my @XMATCH, it doesn't. Could it be an ONIG_OPTION?

Code:
v:\> echo %@regex[\d{1,2},22]
0

v:\> echo %@xmatch[\d{1,2},22]
0
 
#2
Rex, do you have any docs which say whether Onig's PERL syntax honors the PERL quantifier {m,n} (at least m, at most n)?

AFAICT, with your @REGEX and my @XMATCH, it doesn't. Could it be an ONIG_OPTION?

Code:
v:\> echo %@regex[\d{1,2},22]
0

v:\> echo %@xmatch[\d{1,2},22]
0

Did you look into this?

I even tried explicitly:
Code:
psyntax->op2 |= ONIG_SYN_OP2_PLUS_POSSESSIVE_INTERVAL;
(which didn't work).

And does TCC call onig_set_default_syntax()? If so, will that propagate to my DLL (so that I don't have QueryOptionValue)?

Thanks.
 
#4
On Mon, 19 Jul 2010 19:18:17 -0400, you wrote:

|---Quote---
|> ---Quote (Originally by vefatica)---
|> Rex, do you have any docs which say whether Onig's PERL syntax honors
|> the PERL quantifier {m,n} (at least m, at most n)?
|>
|> AFAICT, with your @REGEX and my @XMATCH, it doesn't. Could it be an
|> ONIG_OPTION?
|---End Quote---
|I have no idea.

Aha! ... my fault for not quoting the regex! It contains a comma so
NthArgument() was chopping it up.