Re: semicolon not required on END statement - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: semicolon not required on END statement
Date
Msg-id 200410020048.i920mjB03184@candle.pha.pa.us
Whole thread Raw
In response to Re: semicolon not required on END statement  (Neil Conway <neilc@samurai.com>)
Responses Re: semicolon not required on END statement  (Neil Conway <neilc@samurai.com>)
List 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@postgresql.org so that your
>       message can get through to the mailing list cleanly

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug report
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1276: Backend panics on SETVAL('..', 0)...