Re: WIP: default values for function parameters

From: "Greg Stark" <stark(at)enterprisedb(dot)com>
To: "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>
Cc: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Grzegorz Jaskiewicz" <gj(at)pointblue(dot)com(dot)pl>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Subject: Re: WIP: default values for function parameters
Date: 2008-12-12 15:31:46
Message-ID: 4136ffa0812120731y737f5eb3wfa3f969789581530@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 12, 2008 at 3:11 PM, Dimitri Fontaine
<dfontaine(at)hi-media(dot)com> wrote:
> That's why I'm preferring the common-lisp syntax of :param value, or its
> variant param: value.

FWIW there is no such common-lisp syntax. Colon is just a regular
symbol character and :param is just a regular symbol in common-lisp.
There is a convention that functions parse their argument lists
looking for such tokens as indicators of what to do with the next
argument but it's purely a convention. There's no syntactic
significance to the colon.

A similar problem arises with using Perl as a precedent. => is just a
regular operator in perl which quotes the lhs as a string if it's a
simple token and otherwise behaves just like a comma. That would be
very different from what we're talking about having it do here.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Douglas McNaught 2008-12-12 15:54:18 Re: WIP: default values for function parameters
Previous Message Dimitri Fontaine 2008-12-12 15:11:39 Re: WIP: default values for function parameters