From 311bcfc6b3acdd6fd152798c7f287ddf74fa2a98 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 16 Apr 2024 21:46:48 +0200 Subject: Adding upstream version 15.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/pltcl-procnames.html | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/src/sgml/html/pltcl-procnames.html (limited to 'doc/src/sgml/html/pltcl-procnames.html') diff --git a/doc/src/sgml/html/pltcl-procnames.html b/doc/src/sgml/html/pltcl-procnames.html new file mode 100644 index 0000000..494505c --- /dev/null +++ b/doc/src/sgml/html/pltcl-procnames.html @@ -0,0 +1,13 @@ + +44.12. Tcl Procedure Names
44.12. Tcl Procedure Names
Prev UpChapter 44. PL/Tcl — Tcl Procedural LanguageHome Next

44.12. Tcl Procedure Names

+ In PostgreSQL, the same function name can be used for + different function definitions as long as the number of arguments or their types + differ. Tcl, however, requires all procedure names to be distinct. + PL/Tcl deals with this by making the internal Tcl procedure names contain + the object + ID of the function from the system table pg_proc as part of their name. Thus, + PostgreSQL functions with the same name + and different argument types will be different Tcl procedures, too. This + is not normally a concern for a PL/Tcl programmer, but it might be visible + when debugging. +

Prev Up Next
44.11. PL/Tcl Configuration Home Chapter 45. PL/Perl — Perl Procedural Language
\ No newline at end of file -- cgit v1.2.3