pl/pgsql oddity

[Richard_D_Levine@raytheon.com]

Don't get used to Ada. It's almost as dead as COBOL, though I liked it too
for some things. Oracle plsql is soooo Ada-like I've literally cut and
pasted whole Ada routines into Oracle plsql and they work without
modification. PostgreSQL doesn't do parameters and packages, so it is
slightly more work to move stuff from your front-end into your back-end,
but often worth it.



"Frank D. Engel, Jr."
<fde101@fjrhome.net> To: pgsql-general <pgsql-general@postgresql.org>
Sent by: cc:
pgsql-general-owner@pos Subject: Re: [GENERAL] pl/pgsql oddity
tgresql.org


12/16/2004 03:01 PM






"elsif" is the spelling used by Ada. I'm getting rather used to it,
myself.

I'm really starting to like Ada. So "elsif" is fine with me.

As far as alternate spellings being accepted within a language, look at
the Transcript language used by Runtime Revolution ([url]www.runrev.com[/url]),
which is a so-called "Xtalk" language (based on HyperTalk, which was
used by HyperCard; and yes, HyperTalk was like this too...)

-- and # are synonyms (comment delimiters)

abbreviated can be abbreviated as abbr or abbrev ;-)

audioClip can be abbreviated as ac

accelKey and acceleratorKey

acceleratorModifiers and accelMods

arm and armed

autoHilite and autoHighlight

recentNames and backList

group, background, bg, and bkgnd


The list goes on and On and ON...


On Dec 16, 2004, at 2:12 PM, Guy Rouillier wrote:

> Michael Fuhr wrote:

>> On Thu, Dec 16, 2004 at 12:27:53PM -0500, Geoffrey wrote:
>>

>>> I don't know of any other language that permits multiple spellings
>>> for the same construct. I'd be concerned with starting such a
>>> precedent.

>>
>> I'd be in favor of making it a bloody law that every bloody language
>> use the same bloody spelling. I'm forever forgetting whether a
>> particular language uses ELSE IF, ELSEIF, ELSIF, or ELIF. Grumble,
>> grumble, grumble....

>
> As a relative newbie to PostgreSQL (but an old-timer to programming
> languages and other DMBSs) I would certainly vote for allowing elseif.
> This is my first encounter of "else" without the terminating "e", and
> that would not be a natural omission for me.
>
> --
> Guy Rouillier
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
> joining column's datatypes do not match
>
>

-----------------------------------------------------------
Frank D. Engel, Jr. <fde101@fjrhome.net>

$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten
Son, that whosoever believeth in him should not perish, but have
everlasting life.
$



__________________________________________________ _________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at [url]www.doteasy.com[/url]


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings




---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [email]majordomo@postgresql.org[/email])

[Frank D. Engel, Jr.]

Since when is COBOL dead ;-)

Can't say I know that language yet, actually (I did know some Fortran,
but it's been a while)...


Just because a language is not in common use does not mean it lacks
value. Some ideas are so far ahead of their time, they get laughed off
for a time, then suddenly become so widespread no one would believe
they were ever looked down on.

(The world *is* flat, right?)


On Dec 16, 2004, at 4:18 PM, [email]Richard_D_Levine@raytheon.com[/email] wrote:

> Don't get used to Ada. It's almost as dead as COBOL, though I liked
> it too
> for some things. Oracle plsql is soooo Ada-like I've literally cut and
> pasted whole Ada routines into Oracle plsql and they work without
> modification. PostgreSQL doesn't do parameters and packages, so it is
> slightly more work to move stuff from your front-end into your
> back-end,
> but often worth it.
>
>
>
> "Frank D. Engel, Jr."
> <fde101@fjrhome.net> To:
> pgsql-general <pgsql-general@postgresql.org>
> Sent by: cc:
> pgsql-general-owner@pos Subject: Re:
> [GENERAL] pl/pgsql oddity
> tgresql.org
>
>
> 12/16/2004 03:01 PM
>
>
>
>
>
>
> "elsif" is the spelling used by Ada. I'm getting rather used to it,
> myself.
>
> I'm really starting to like Ada. So "elsif" is fine with me.
>
> As far as alternate spellings being accepted within a language, look at
> the Transcript language used by Runtime Revolution ([url]www.runrev.com[/url]),
> which is a so-called "Xtalk" language (based on HyperTalk, which was
> used by HyperCard; and yes, HyperTalk was like this too...)
>
> -- and # are synonyms (comment delimiters)
>
> abbreviated can be abbreviated as abbr or abbrev ;-)
>
> audioClip can be abbreviated as ac
>
> accelKey and acceleratorKey
>
> acceleratorModifiers and accelMods
>
> arm and armed
>
> autoHilite and autoHighlight
>
> recentNames and backList
>
> group, background, bg, and bkgnd
>
>
> The list goes on and On and ON...
>
>
> On Dec 16, 2004, at 2:12 PM, Guy Rouillier wrote:
>

>> Michael Fuhr wrote:

>>> On Thu, Dec 16, 2004 at 12:27:53PM -0500, Geoffrey wrote:
>>>
>>>> I don't know of any other language that permits multiple spellings
>>>> for the same construct. I'd be concerned with starting such a
>>>> precedent.
>>>
>>> I'd be in favor of making it a bloody law that every bloody language
>>> use the same bloody spelling. I'm forever forgetting whether a
>>> particular language uses ELSE IF, ELSEIF, ELSIF, or ELIF. Grumble,
>>> grumble, grumble....

>>
>> As a relative newbie to PostgreSQL (but an old-timer to programming
>> languages and other DMBSs) I would certainly vote for allowing elseif.
>> This is my first encounter of "else" without the terminating "e", and
>> that would not be a natural omission for me.
>>
>> --
>> Guy Rouillier
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 9: the planner will ignore your desire to choose an index scan if
>> your
>> joining column's datatypes do not match
>>
>>

> -----------------------------------------------------------
> Frank D. Engel, Jr. <fde101@fjrhome.net>
>
> $ ln -s /usr/share/kjvbible /usr/manual
> $ true | cat /usr/manual | grep "John 3:16"
> John 3:16 For God so loved the world, that he gave his only begotten
> Son, that whosoever believeth in him should not perish, but have
> everlasting life.
> $
>
>
>
> __________________________________________________ _________
> $0 Web Hosting with up to 120MB web space, 1000 MB Transfer
> 10 Personalized POP and Web E-mail Accounts, and much more.
> Signup at [url]www.doteasy.com[/url]
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> [email]majordomo@postgresql.org[/email])
>
>

-----------------------------------------------------------
Frank D. Engel, Jr. <fde101@fjrhome.net>

$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten
Son, that whosoever believeth in him should not perish, but have
everlasting life.
$



__________________________________________________ _________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at [url]www.doteasy.com[/url]


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

[url]http://archives.postgresql.org[/url]

[Bruno Wolff III]

On Thu, Dec 16, 2004 at 15:34:03 -0500,
[email]Richard_D_Levine@raytheon.com[/email] wrote:

> I prefer the FORTRAN66 construct
>
> IF <condition> <label1> <label2> <label3>

My memory is that those labels were separated by commas.

>
> where it jumps to label1 if <condition> is negative, label2 if zero, and
> label3 if positive. No else ifs about it.
>
> I hope you realize I'm as kidding as I am obviously too old.

As long as you are dredging up old Fortran; in my opinion computed
gotos were harder to follow than the ones based on the sign of an expression.

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [email]majordomo@postgresql.org[/email])

[Neil Conway]

On Thu, 2004-12-16 at 11:09 -0500, Tom Lane wrote:

> I think we should go ahead and do that for 8.0. I'm getting tired of
> reading reports that stem from this mistake (I think this is the third
> one in the past month ...). I can't see any real downside to accepting
> both spellings, can you?

I agree this is pretty harmless. I've applied the attached trivial patch
to HEAD.

-Neil



---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster