Nathan Myers <[EMAIL PROTECTED]> writes: > - Keep the name 'C' for both old-style and new-style module declarations. > - Require that new-style modules define a distinguished symbol, such as > "int __postgresql_call_7_1;". I was thinking along the same lines myself. I'd want to do it on a per-function basis, though, rather than assuming that all functions in a module must use the same interface. I'd be inclined to define a macro that creates the signal object, so that you'd write something like PG_FUNCTION_API_V2(foo); Datum foo(PG_FUNCTION_ARGS) { ... } to create a dynamically loadable new-style function. Comments? regards, tom lane
- [HACKERS] [rfc] new CREATE FUNCTION (and more) Marko Kreen
- Re: [HACKERS] [rfc] new CREATE FUNCTION (and more) Tom Lane
- Re: [HACKERS] [rfc] new CREATE FUNCTION (and more) Bruce Momjian
- Re: [HACKERS] [rfc] new CREATE FUNCTION (and more) Marko Kreen
- Re: [HACKERS] [rfc] new CREATE FUNCTION (and more) Nathan Myers
- Re: [HACKERS] [rfc] new CREATE FUNCTION (and mo... Tom Lane
- Re: [HACKERS] [rfc] new CREATE FUNCTION (an... Philip Warner
- Re: [HACKERS] [rfc] new CREATE FUNCTIO... Tom Lane
- Re: [HACKERS] [rfc] new CREATE FUN... Philip Warner
- Re: [HACKERS] [rfc] new CREATE... Tom Lane
- Re: [HACKERS] [rfc] new CREATE... Philip Warner
- Re: [HACKERS] [rfc] new CREATE... Tom Lane
- Re: [HACKERS] [rfc] new CREATE... Philip Warner
- Re: [HACKERS] [rfc] new CREATE... Tom Lane
- Re: [HACKERS] [rfc] new CREATE... Tom Lane
- Re: [HACKERS] [rfc] new CREATE FUNCTION (an... Marko Kreen