Hi Christian -- Sorry about the delay. The patch is based on PG version
9.5.3.
The commit history of the repo should give a high-level idea of the changes
required in PG to support compilation by a C++ compiler. I presume that
Peter's patch would be easier to integrate into PG. In any case, I would
On Sun, Aug 14, 2016 at 5:05 PM, Joy Arulraj wrote:
> Hi folks --
>
> We have ported Postgres over to the C++ language (C++11 standard).
>
> https://github.com/jarulraj/postgresql-cpp
>
> Our goal is to use certain features of the C++ language and its standard
> library to simplify coding, improve
On 8/16/16 2:52 AM, Gavin Flower wrote:
In both cases, part of the motivation to change from C was to appeal to
new developers - from what I remember of the discussions.
I have moved this discussion over to -hackers.
(https://www.postgresql.org/message-id/f7682c24-4271-1ff5-d963-053ecb0fc...@b
Thanks, I do hope so.
On Tue, Aug 16, 2016 at 7:00 AM, FarjadFarid(ChkNet) <
farjad.fa...@checknetworks.com> wrote:
> Well done. This is a much needed conversion. As Peter’s article says, it
> does open up more opportunities.
>
>
>
> *From:* pgsql-general-ow...@postgresql.org [mailto:pgsql-gener
On Tue, Aug 16, 2016 at 3:52 AM, Gavin Flower wrote:
> On 16/08/16 18:24, dandl wrote:
>
>>
>> Just wondering what the end goal is for this project... Is it to just
>> maintain an up to date Postgres fork that will compile with a C++ compiler?
>> Is it to get a conversation going for a direction
Well done. This is a much needed conversion. As Peter’s article says, it does
open up more opportunities.
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Joy Arulraj
Sent: 14 August 2016 22:06
To: pgsql-general@postgresql.org
Subject: [GENER
On 16/08/16 18:24, dandl wrote:
Just wondering what the end goal is for this project... Is it to just
maintain an up to date Postgres fork that will compile with a C++
compiler? Is it to get a conversation going for a direction for
Postgres itself to move? The former I don't see gaining much
Just wondering what the end goal is for this project... Is it to just maintain
an up to date Postgres fork that will compile with a C++ compiler? Is it to get
a conversation going for a direction for Postgres itself to move? The former I
don't see gaining much traction or doing all that much fo
Just wondering what the end goal is for this project... Is it to just
maintain an up to date Postgres fork that will compile with a C++ compiler?
Is it to get a conversation going for a direction for Postgres itself to
move? The former I don't see gaining much traction or doing all that much
for t
Kang -- Yes, this is one of the reasons why we chose to do this.
John -- We have not compiled it with non-GCC compilers. But, I presume that
the changes required to support compilation with other compilers should be
minimal as we don't rely on any compiler-specific features.
On Sun, Aug 14, 2016
I agree with this project, I dont like any setjmp/longjmp and the
like. It just fighting against the nature of c++ language. Building
either from scratch gcc48 or clang381 were easy nowdays on either old
linux debian squeeze or centos 5. PS: I had this requirement
circumtances.
On 8/15/16, Joy Aru
Hi Dmitry -- We currently don't use exceptions, but we can certainly use
them in the port. We can also use STL and smart pointers to simplify
development and minimize memory bugs.
On Aug 14, 2016 5:41 PM, "Dmitry Igrishin" wrote:
> Hi Joy,
>
> 2016-08-15 0:05 GMT+03:00 Joy Arulraj :
> > Hi folks
Hi Joy,
2016-08-15 0:05 GMT+03:00 Joy Arulraj :
> Hi folks --
>
> We have ported Postgres over to the C++ language (C++11 standard).
>
> https://github.com/jarulraj/postgresql-cpp
>
> Our goal is to use certain features of the C++ language and its standard
> library to simplify coding, improve cod
On 8/14/2016 2:05 PM, Joy Arulraj wrote:
We have ported Postgres over to the C++ language (C++11 standard).
https://github.com/jarulraj/postgresql-cpp
Our goal is to use certain features of the C++ language and its
standard library to simplify coding, improve code reuse, and avoid
bugs. Pete
14 matches
Mail list logo
