From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <neilc(at)samurai(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pl/pgsql: END verbosity |
Date: | 2005-06-22 03:11:38 |
Message-ID: | 3601.24.211.165.134.1119409898.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Neil Conway said:
> In PL/PgSQL, "END LOOP" is used to terminate loop blocks, and "END IF"
> is used to terminate IF blocks. This is needlessly verbose: we could
> simply accept "END" in both cases without syntactic ambiguity. I'd like
> to make this change, so that END can be used to terminate any kind of
> block. There's no need to remove support for the present syntax, of
> course, so there's no backward compatibility concern. Oracle's PL/SQL
> does require "END IF" and "END LOOP", but folks interested in maximum
> compatibility can always use those forms if they like.
>
> Any objections?
>
I'm unkeen. I see no technical advantage - it's just a matter of taste. We
advertise that plpgsql is similar to plsql - we should not do anything to
make that less so IMNSHO. Terseness is not always good, redundancy is not
always bad.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-22 03:21:37 | Re: Problem with dblink regression test |
Previous Message | Bruce Momjian | 2005-06-22 03:10:40 | Re: pg_terminate_backend idea |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-22 03:21:37 | Re: Problem with dblink regression test |
Previous Message | Pavel Stehule | 2005-06-22 02:59:05 | Re: Function's LEAST, GREATEST and DECODE (Oracle vararg |