Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: PL/Tcl implementation


  • From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: fschmidt <fschmidt(at)gmail(dot)com>
  • Cc: pgsql-general(at)postgresql(dot)org
  • Subject: Re: PL/Tcl implementation
  • Date: Thu, 31 Jan 2008 23:16:09 -0300
  • Message-id: <20080201021609.GD14696@alvh.no-ip.org> <text/plain>

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.



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group