PL/Tcl implementation
Why doesn't the PL/Tcl (and PL/Python) implementation use the SPI functions?
For example pltcl_set_tuple_values() calls NameStr() instead of SPI_fname()
and heap_getattr() instead of SPI_getbinval(). Why? This makes the code
impossible to follow for someone who is not familiar with the postgres
source and has only read the online documentation.
--
View this message in context: http://www.nabble.com/PL-Tcl-implementation-tp15215251p15215251.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
fschmidt escribi�:
Why doesn't the PL/Tcl (and PL/Python) implementation use the SPI functions?
For example pltcl_set_tuple_values() calls NameStr() instead of SPI_fname()
and heap_getattr() instead of SPI_getbinval(). Why? This makes the code
impossible to follow for someone who is not familiar with the postgres
source and has only read the online documentation.
If you are reading the PL/Tcl source (i.e. the Postgres source, really),
you should definitely be using a source code cross-referencing system;
be it doxygen, or cscope, glimpse, or whatever tool fits the bill. If
you cannot find out at a keystroke where to find the definition of
NameStr() you are doomed [to take a lot longer to understand what's
going on].
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.