Re: semicolon not required on END statement

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hussein Patni <security(at)cosbit(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: semicolon not required on END statement
Date: 2004-10-02 00:48:45
Message-ID: 200410020048.i920mjB03184@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Improved wording that doesn't telegraph, "Look at me!":

Each declaration and each statement within a block is terminated by a
semicolon, though the final <literal>END</literal> that concludes a
function does not require one.

---------------------------------------------------------------------------

Neil Conway wrote:
> On Fri, 2004-10-01 at 13:46, Tom Lane wrote:
> > We specifically do not require a semicolon at the very end of the
> > function definition.
>
> Yeah, makes sense. Attached is a doc patch. Barring any objections I'll
> apply it to HEAD by end-of-day today.
>
> -Neil
>

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-10-03 05:10:03 BUG #1276: Backend panics on SETVAL('..', 0)...
Previous Message Tom Lane 2004-10-01 22:58:00 Re: Bug report