From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Cc: | "Nicolas Barbier" <nicolas(dot)barbier(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Documentation patch: change a name in a grammar rule |
Date: | 2006-04-17 17:09:51 |
Message-ID: | 200604171909.51872.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Nicolas Barbier wrote:
> In for example set.sgml, just "name" is used for the exact same
> concept. I changed the patch so that "varname" is used, because
> "name" was already in use by this specific grammar. Maybe the usage
> of "var" makes it less clear indeed, for people that know that those
> things are always referred to as "parameters" and never as
> "variables".
A variable would be something that you store application data in,
whereas a parameter is some nondata value that influences your
calculations. That's my recollection of how the terms are used in
mathematics. So parameter is decidedly the better term than variable.
If that is confusing, make it config_param or something like that.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-04-17 18:11:16 | Re: pg_ctl options checking |
Previous Message | Peter Eisentraut | 2006-04-17 17:00:06 | Re: pg_ctl options checking |