Re: Future of our regular expression code

Поиск
Список
Период
Сортировка
От Billy Earney
Тема Re: Future of our regular expression code
Дата
Msg-id CAB1ii-f5OLZqvx57BTE+RD7jr26NVXtEQtBm8UcFzUvBPyw-Xw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Future of our regular expression code  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Future of our regular expression code  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
Thanks Tom.  I looked at the code in the libraries I referred to earlier, and it looks like the code in the regex
directoryis exactly the same as Walter Waldo's version, which has at least one comment from the middle of last decade
(~2003).   Has people thought about migrating to the pcre library?  It seems to have a lot of neat features, and also
hasa jit, and it looks like it is being actively maintained and has decent comments.<br /><br /><br /><div
class="gmail_quote">OnSun, Feb 19, 2012 at 7:40 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">Billy Earney <<a
href="mailto:billy.earney@gmail.com">billy.earney@gmail.com</a>>writes:<br /> > I did a google search, and found
thefollowing:<br /> > <a href="http://www.arglist.com/regex/" target="_blank">http://www.arglist.com/regex/</a><br
/><br/></div>Hmm ... might be worth looking at those two pre-existing attempts at<br /> making a standalone library
fromHenry's code, just to see what choices<br /> they made.<br /><div class="im"><br /> > Which states that Tcl uses
thesame library from Henry.  Maybe someone<br /> > involved with that project would help explain the library?<br
/><br/></div>Um ... did you see the head message in this thread?<br /><br />                        regards, tom
lane<br/></blockquote></div><br /> 

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: leakproof
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: Future of our regular expression code