From: | "Nicolas Barbier" <nicolas(dot)barbier(at)gmail(dot)com> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Documentation patch: change a name in a grammar rule |
Date: | 2006-04-17 21:50:12 |
Message-ID: | b0f3f5a10604171450p47617babn69a825c1914dba73@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
2006/4/17, Peter Eisentraut <peter_e(at)gmx(dot)net>:
> 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.
Updated patch attached. We just had another person that made the
mistake, hopefully making up for the time and resources I'm depriving
you guys of :-).
Nicolas
--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html
Attachment | Content-Type | Size |
---|---|---|
pgsql_doc_alter_role_clarification_3.patch | text/x-patch | 2.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-04-17 22:13:07 | Re: pg_ctl options checking |
Previous Message | Sven Suursoho | 2006-04-17 20:26:07 | Re: plpython improvements |