At 10:48 AM 22/12/2004 -0500, you wrote:

> >"Geoff Worboys" <geoff@...> wrote:
> >
> >
> >Now we have:
> >
> >CREATE PROCEDURE P RETURNS (X INT)
> >BEGIN
> > X = 0;
> > SUSPEND;
> >END
> >
> >And by design it has two compatible execution methods. And we must preserve
> >it, not because it's a legacy stuff, but because it's a useful feature,
> >IMHO.
> >

Jim wrote:

>I don't particularly care about this case, but it raises a question
>worth discussing, which is what legacy behaviors should be preserved?

One example is this (commonly recommended to BDE users in those bad old
days, is probably still being recommended in some form with generic
interfaces like ADO and JDBC and is still rife in legacy code):

CREATE PROCEDURE GET_PK (AINPUT SMALLINT)
RETURNS (X INT)
AS BEGIN
X = GEN_ID(AGENERATOR, :AINPUT);
SUSPEND;
END

It is used indiscriminately AC/DC.

Helen