RE: as or is
- From: "MacGregor, Ian A." <ian@xxxxxxxxxxxxxxxxx>
- To: <BoivinP@xxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 10 Sep 2004 07:06:24 -0700
The following is pure cojecture ...
Both exist for for grammatical reasons. "Create Package <package_name> =
is" is grating. "Create" is the verb. What's the "is" doing there. =
However, inside the package one doesn't use the verb "create" in =
defining procdeures. "Procedure <procedure_name> is" has a verb; =
"Procedure <procedure_name> as" does not. Tnen they using is in =
certain cases and as in others was confusing and allowed both.=20
PL/SQL has had is and as from the beginning. What about Ada?
Ian MacGregor
Stanford Linear Accelerator Center
ian@xxxxxxxxxxxxxxxxx
=20
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Boivin, Patrice J
Sent: Thursday, September 09, 2004 7:12 AM
To: 'oracle-l@xxxxxxxxxxxxx'
Subject: as or is
This is out of curiosity...
Why, in the CREATE PACKAGE, or CREATE PACKAGE BODY statements, does =
Oracle list both IS and AS as possible elements?
Is it a backward-compatibility thing?
I find it weird that both would be in the command diagrams. I like =
things nice and simple.
: )
Patrice.
--
To unsubscribe - =
mailto:oracle-l-request@xxxxxxxxxxxxx&subject=3Dunsubscribe
To search the archives - //www.freelists.org/archives/oracle-l/
--
To unsubscribe - mailto:oracle-l-request@xxxxxxxxxxxxx&subject=unsubscribe
To search the archives - //www.freelists.org/archives/oracle-l/
Other related posts:
