| From: | Marc Lavergne <mlavergne-pub(at)richlava(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | C vs. C++ contributions |
| Date: | 2002-07-21 19:20:34 |
| Message-ID: | 3D3B0982.3020709@richlava.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am working on a rather extensive Oracle compatibility layer that I use
with PostgreSQL. I am considering contributing the code back to the
project but the problem is that the layer is currently implemented in
C++. Simply looking throughout the sources and the dev FAQ, there's
never any mention of C++ (libpq++ excepted). So, at a risk of stating
the obvious (and I'm 99.99% sure I am), does backend code need to be
submitted as C even if it's for an entirely NEW module?
Thanks,
Marc L.
PS: (Background) The code originally started out as client-side C++ code
for a project but I'm seeing the value of it for the server side for
achieving SQL*Net compatibility.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2002-07-21 21:08:58 | Heap tuple header, vacation |
| Previous Message | Gustavo Gonzalez Giron | 2002-07-21 18:11:54 | Fwd: XPg: a new Java PostgreSQL Interface |