| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Gaetano Mendola <mendola(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: C++ compiler |
| Date: | 2013-06-25 00:19:39 |
| Message-ID: | 51C8E21B.9060101@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/24/2013 04:59 PM, Bruce Momjian wrote:
>
> On Thu, Jun 20, 2013 at 12:45:48PM +0800, Craig Ringer wrote:
>> I see value in making the codebase compileable with g++... and down the
>> track I can see being able to use basic class features as quite useful
>> given Pg's fairly OO internal design. Inline template functions instead
>> of macros would be nice. I've worked with C++ enough not to be overly
>> excited by the idea of going down the rabbit hole of Boost, complex
>> template arrangements, etc, and I don't love the STL ... but any
>> sensible project adopting C++ carefully picks and chooses what features
>> it uses and how.
>
> I think the big question is whether you can _control_ what C++ features
> are used, or whether you are perpetually instructing users what C++
> features not to use.
How is that different than us having to do the same with C?
JD
>
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2013-06-25 00:21:26 | Re: C++ compiler |
| Previous Message | Bruce Momjian | 2013-06-24 23:59:06 | Re: C++ compiler |