Peter Eisentraut <pete...@gmx.net> writes: > What is the difference (on affected platforms) between
> Datum funcname(PG_FUNCTION_ARGS); > and writing (effectively) > PGDLLEXPORT Datum funcname(PG_FUNCTION_ARGS); > Datum funcname(PG_FUNCTION_ARGS); > or for that matter > Datum funcname(PG_FUNCTION_ARGS); > PGDLLEXPORT Datum funcname(PG_FUNCTION_ARGS); According to http://www.postgresql.org/message-id/52d25aa2.50...@2ndquadrant.com the latter fails outright. Which is problematic because that'd be the more common case (particularly if you put manually-written externs in a header file). So while we could do this, and it'd probably be an improvement in the very long run, it'd definitely cause pain in the short run. Not sure if it's worth it. I still wish we could get rid of this problem by fixing the Windows build recipes so that the PGDLLEXPORT marking wasn't needed. We proved to ourselves recently that getting rid of PGDLLIMPORT on global variables wouldn't work, but I'm not sure that the function end of it was really investigated. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
