From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Kurt Harriman <harriman(at)acm(dot)org> |
Subject: | Re: Mostly Harmless: Welcoming our C++ friends |
Date: | 2008-12-07 16:44:08 |
Message-ID: | 493BFD58.6060709@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> On Saturday 06 December 2008 22:38:29 James Mansion wrote:
>
>> Kurt Harriman wrote:
>>
>>> The foremost opposing argument seems to have been that there
>>> should be no attempt to alleviate the existing reserved word
>>> problem without automatic enforcement to guarantee that never
>>> in the future can new occurrences be introduced.
>>>
>> Is there anything in the source that would necessarily preclude using the
>> C++ compiler to build *all* the code?
>>
>
> Probably lots, but that's not the problem we are trying to solve here. And
> many people are seriously not interested in using C++ for PostgreSQL.
>
>
The most serious problem AFAIK is that we use setjmp/longjmp, which I
understand does not play at all nicely with C++ exceptions.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2008-12-07 16:48:20 | Re: BUG #4186: set lc_messages does not work |
Previous Message | Andrew Dunstan | 2008-12-07 16:41:11 | Re: user-based query white list |