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 at 6:30 PM, kang joni <kangjon...@gmail.com> wrote: > 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 Arulraj <jarul...@cs.cmu.edu> wrote: > > 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" <dmit...@gmail.com> wrote: > > > >> Hi Joy, > >> > >> 2016-08-15 0:05 GMT+03:00 Joy Arulraj <jarul...@cs.cmu.edu>: > >> > 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 code reuse, and avoid bugs. > Peter's > >> > article titled `Moving to C++` was a source of inspiration for us. > >> What about the exceptions? Are you using them? > >> > >> -- > >> // Dmitry. > >> > > >
