Re: Flex / Regexps (Re: awk regex bug)

2015-06-08 Thread hruodr
I wrote: > [...] Why should > be difficult to track the indices in yytext of the beginning and the end > of each matching subexpression, in two arrays of integers (one for > the beginning and one for the end)? [...] More exactly: in the first array the index of the first element of the matching

Flex / Regexps (Re: awk regex bug)

2015-06-08 Thread hruodr
Otto Moerbeek wrote: > Refering to subpatterns is not available in flex. I suppose it is not > available since it would require a more complex re engine. > Interpretation of the lexical value should be "hand-crafted". I also though caomplexity can be the reason, but I have doubts. Why should b

Re: awk regex bug

2015-06-08 Thread Otto Moerbeek
On Mon, Jun 08, 2015 at 02:49:44PM +, hru...@gmail.com wrote: > Otto Moerbeek wrote: > > > Tradiotionally, { } pattersn are not part of awk re's. > > > > Posix added them, but we do not include them afaik. Gnu awk only accepts > > them if given an extra arg (--posix or --re-interval). > > >

Re: awk regex bug

2015-06-08 Thread hruodr
Otto Moerbeek wrote: > Tradiotionally, { } pattersn are not part of awk re's. > > Posix added them, but we do not include them afaik. Gnu awk only accepts > them if given an extra arg (--posix or --re-interval). > > I think this should be documented. Although there is a clear theory about "regul

Re: awk regex bug

2015-05-28 Thread Otto Moerbeek
On Thu, May 28, 2015 at 02:08:47AM -0500, cwl...@mst.edu wrote: > Hi misc, > > I'm running a 5.7 release, and I'm wondering if anyone can confirm > an awk bug I found. > > Curly brackets are treated as literal characters instead of bounds > as specified by re_format(7). > > Reproduction: > > e