From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Jacob Rief <jacob(dot)rief(at)gmx(dot)at> |
Subject: | Re: Writing triggers in C++ |
Date: | 2007-02-13 23:57:31 |
Message-ID: | 200702140057.31743.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jacob Rief wrote:
> Is there any convention how to rename such identifiers? If I would
> rename those identifiers (I simply would add an underscore to each of
> them), would such a patch be accepted and adopted onto one of the
> next releases?
Couldn't you do the required renamings as preprocessor macros, e.g.,
#define typename _typename
#include <postgres_stuff>
#undef typename
#include <c++_stuff>
your_code;
I would expect very little enthusiasm for making PostgreSQL code C++
safe. There is already too much trouble keeping up with all the
variants of C.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Dunstan | 2007-02-14 00:03:47 | Re: Enums patch v2 |
Previous Message | Peter Eisentraut | 2007-02-13 23:53:27 | Fixing insecure security definer functions |