From: | Andreas Seltenreich <andreas+pg(at)gate450(dot)dyndns(dot)org> |
---|---|
To: | Mark Dilger <pgsql(at)markdilger(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PG Extensions: Must be statically linked? |
Date: | 2006-03-03 21:53:07 |
Message-ID: | 87mzg78abg.fsf@gate450.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mark Dilger writes:
> I have had the same concern, though never any hard evidence of a
> problem. If the C++ functions are wrapped with "extern C", and all
> exceptions caught (perhaps converted into error numbers which are then
> returned from the wrapper functions to the plain-C calling functions),
> are there any remaining known problems? I have often considered
> making a C++ allocator which wrapped palloc and pfree, so that I could
> then use the STL within the backend...
>
> Has anyone tried this?
I did some experiments on a C++ language handler last year (including
an allocator and a class loader to spare the extern "C"s/name
mangling):
<http://archives.postgresql.org/pgsql-general/2005-10/msg01570.php>
<news:87acgxjzsl(dot)fsf(at)gate450(dot)dyndns(dot)org>
The remaining issue is the impedance mismatch between longjmp()ing and
exceptions.
regards,
Andreas
--
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-03 22:02:00 | Re: [PATCHES] [HACKERS] Online backup vs Continuous backup |
Previous Message | Bruce Momjian | 2006-03-03 21:36:36 | Re: Building Windows Server Extensions Using VC++ 2005 |