Re: PG Extensions: Must be statically linked?
От | Andreas Seltenreich |
---|---|
Тема | Re: PG Extensions: Must be statically linked? |
Дата | |
Msg-id | 87mzg78abg.fsf@gate450.dyndns.org обсуждение исходный текст |
Ответ на | Re: PG Extensions: Must be statically linked? (Mark Dilger <pgsql@markdilger.com>) |
Список | 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.fsf@gate450.dyndns.org> The remaining issue is the impedance mismatch between longjmp()ing and exceptions. regards, Andreas --
В списке pgsql-hackers по дате отправления: