Bikeshedding on enum vocabulary

From: Aidan Van Dyk <aidan(at)highrise(dot)ca>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Bikeshedding on enum vocabulary
Date: 2010-10-27 15:16:03
Message-ID: AANLkTi=aHU0uR=vrztJsbHUGYZY_RfEqvX+bU-29Ji3Y@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 27, 2010 at 10:57 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:

> Wow, this must be the most difficult smallest thing I have ever seen
> discussed in pg-hackers.  It doesn't seem like there are enough votes
> in any particular direction.  Now *this* is proper bikeshedding.
>
> Should we ask more openly in another thread, with a different, more
> catchy subject?

Well, as someone coming to enums from a C/C++ background, element is
the last thing I would have thought. _My_ scale of intuitiveness is:

1) label (my normal vocabulary when talking about enums)
2) identifier [constant] (when talking spec-type jargon)

Never have I thought of the enum label as either a "value", or an
"element". That's not to say anyone else hasn't thought of them
differently. Obvously ;-)

</bikeshed>

--
Aidan Van Dyk                                             Create like a god,
aidan(at)highrise(dot)ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-10-27 15:41:00 Re: plan time of MASSIVE partitioning ...
Previous Message Alvaro Herrera 2010-10-27 15:06:17 Re: xlog.c: WALInsertLock vs. WALWriteLock