Re: Future of our regular expression code - Mailing list pgsql-hackers
From | Billy Earney |
---|---|
Subject | Re: Future of our regular expression code |
Date | |
Msg-id | CAB1ii-d1o0O2ch_9hofFdMGaZ63oyEnrCL948eqsTxvxb_8BQQ@mail.gmail.com Whole thread Raw |
In response to | Re: Future of our regular expression code (Tom Lane <tgl@sss.pgh.pa.us>) |
Responses |
Re: Future of our regular expression code
|
List | pgsql-hackers |
Tom,<br /><br />I did a google search, and found the following:<br /><a href="http://www.arglist.com/regex/">http://www.arglist.com/regex/</a><br/><br />Which states that Tcl uses the same libraryfrom Henry. Maybe someone involved with that project would help explain the library? Also I noticed at the url aboveis a few ports people did from Henry's code. I didn't download and analyze their code, but maybe they have made somecomments that could help, or maybe have some improvements to the code.. <br /><br />Just a thought.. :)<br /><br />BillyEarney<br /><br /><div class="gmail_quote">On Sun, Feb 19, 2012 at 5:42 PM, Tom Lane <span dir="ltr"><<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote" style="margin:00 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Brendan Jurd <<a href="mailto:direvus@gmail.com">direvus@gmail.com</a>>writes:<br /> > Are you far enough into the backrefs bug thatyou'd prefer to see it<br /> > through, or would you like me to pick it up?<br /><br /></div>Actually, what I've beendoing today is a brain dump. This code is<br /> never going to be maintainable by anybody except its original author<br/> without some internals documentation, so I've been trying to write<br /> some based on what I've managed to reverse-engineerso far. It's<br /> not very complete, but I do have some words about the DFA/NFA stuff,<br /> which I willprobably revise and fill in some more as I work on the<br /> backref fix, because that's where that bug lives. I havealso got<br /> a bunch of text about the colormap management code, which I think<br /> is interesting right now becausethat is what we are going to have<br /> to fix if we want decent performance for Unicode \w and related<br /> classes(cf the other current -hackers thread about regexes).<br /> I was hoping to prevail on you to pick that part up asyour first<br /> project. I will commit what I've got in a few minutes --- look<br /> for src/backend/regex/README inthat commit. I encourage you to<br /> add to that file as you figure stuff out. We could stand to upgrade<br /> a lotof the code comments too, of course, but I think a narrative<br /> description is pretty useful before diving into code.<br/><br /> regards, tom lane<br /><div class="HOEnZb"><div class="h5"><br /> --<br /> Sent viapgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br /> To makechanges to your subscription:<br /><a href="http://www.postgresql.org/mailpref/pgsql-hackers" target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></div></div></blockquote></div><br />
pgsql-hackers by date: