Re: tsearch in core patch, for inclusion - Mailing list pgsql-hackers

From Brian Hurt
Subject Re: tsearch in core patch, for inclusion
Date
Msg-id 45DC5BF9.4020102@janestcapital.com
Whole thread Raw
In response to Re: tsearch in core patch, for inclusion  (Markus Schiltknecht <markus@bluegap.ch>)
List pgsql-hackers
Markus Schiltknecht wrote:<br /><blockquote cite="mid45DC57EC.1010909@bluegap.ch" type="cite">Hi, <br /><br /> I
recallhaving read something about rewriting the parser. Together with Tom being worried about parser performance and
knowingGCC has switched to a hand written parser some time ago, I suspected bison to be slow. That's why I've asked.
<br/><br /></blockquote> This has little to do with performance and everything to do with the insanity which is C++:<br
/><aclass="moz-txt-link-freetext"
href="http://gnu.teleglobe.net/software/gcc/gcc-3.4/changes.html">http://gnu.teleglobe.net/software/gcc/gcc-3.4/changes.html</a><br
/><br/><blockquote type="cite"><ul><li>A hand-written recursive-descent C++ parser has replaced the YACC-derived C++
parserfrom previous GCC releases. The new parser contains much improved infrastructure needed for better parsing of C++
sourcecodes, handling of extensions, and clean separation (where possible) between proper semantics analysis and
parsing.The new parser fixes many bugs that were found in the old parser. </ul></blockquote><br /> Short form: C++ is
basicallynot LALR(1) parseable.<br /><br /> Brian<br /><br /> 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: tsearch in core patch, for inclusion
Next
From: Bruce Momjian
Date:
Subject: Re: Column storage positions