From 91e79260f636ab4d5a43910b6a38bc75651ad14c Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 24 May 2015 12:20:23 -0400 Subject: Remove no-longer-required function declarations. Remove a bunch of "extern Datum foo(PG_FUNCTION_ARGS);" declarations that are no longer needed now that PG_FUNCTION_INFO_V1(foo) provides that. Some of these were evidently missed in commit e7128e8dbb305059, but others were cargo-culted in in code added since then. Possibly that can be blamed in part on the fact that we'd not fixed relevant documentation examples, which I've now done. --- doc/src/sgml/event-trigger.sgml | 2 -- doc/src/sgml/gist.sgml | 9 --------- doc/src/sgml/trigger.sgml | 4 ---- 3 files changed, 15 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml index 0cb31a478fa..b6cbb1bc249 100644 --- a/doc/src/sgml/event-trigger.sgml +++ b/doc/src/sgml/event-trigger.sgml @@ -998,8 +998,6 @@ typedef struct EventTriggerData PG_MODULE_MAGIC; -Datum noddl(PG_FUNCTION_ARGS); - PG_FUNCTION_INFO_V1(noddl); Datum diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml index dd5d6f9fea0..2d1a5aa863f 100644 --- a/doc/src/sgml/gist.sgml +++ b/doc/src/sgml/gist.sgml @@ -327,7 +327,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_consistent(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_consistent); Datum @@ -390,7 +389,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_union(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_union); Datum @@ -464,7 +462,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_compress(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_compress); Datum @@ -525,7 +522,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_decompress(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_decompress); Datum @@ -565,7 +561,6 @@ LANGUAGE C STRICT; -- in some cases penalty functions need not be strict And the matching code in the C module could then follow this skeleton: -Datum my_penalty(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_penalty); Datum @@ -614,7 +609,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_picksplit(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_picksplit); Datum @@ -721,7 +715,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_same(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_same); Datum @@ -772,7 +765,6 @@ LANGUAGE C STRICT; And the matching code in the C module could then follow this skeleton: -Datum my_distance(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_distance); Datum @@ -859,7 +851,6 @@ LANGUAGE C STRICT; The matching code in the C module could then follow this skeleton: -Datum my_fetch(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(my_fetch); Datum diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml index bd0d71e0d92..52f28bca7a6 100644 --- a/doc/src/sgml/trigger.sgml +++ b/doc/src/sgml/trigger.sgml @@ -709,11 +709,7 @@ CREATE TABLE ttest ( #include "commands/trigger.h" /* ... triggers ... */ #include "utils/rel.h" /* ... and relations */ -#ifdef PG_MODULE_MAGIC PG_MODULE_MAGIC; -#endif - -extern Datum trigf(PG_FUNCTION_ARGS); PG_FUNCTION_INFO_V1(trigf); -- cgit v1.2.3