Re: Lisp as procedural language

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "Vladimir V(dot) Zolotych" <gsmith(at)eurocom(dot)od(dot)ua>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Lisp as procedural language
Date: 2001-05-06 05:12:45
Message-ID: 27162.989125965@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> This must have been an artifact from the time when part of the Postgres
> system was written in Lisp. A Lisp procedural language never actually
> existed in PostgreSQL.

[ Digs in archives... ] The pg_language entry that Vladimir refers to
was still present as late as Postgres 6.5 --- but I agree that it must
have been vestigial long before that. Certainly, at one time large
chunks of Postgres *were* written in Lisp, and I imagine that the
pg_language entry did something useful when that was true. But it was
dead code in Postgres 4.2 (1994), which is the oldest source I have;
there is no Lisp code remaining in 4.2.

It'd theoretically be possible to support Lisp in the same way as we
currently support Tcl, Perl, etc. The hard part is to find a suitable
interpreter that is designed to be dynamically linked into other
applications. Perl still hasn't got that quite right, and I imagine
it's an even more foreign idea for most Lisp systems...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2001-05-06 07:47:11 Re: [HACKERS] MULTIBYTE and SQL_ASCII (was Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars?)
Previous Message mlw 2001-05-06 02:10:33 Re: File system performance and pg_xlog