[perl #53808] elseif should be elsif at blahblah.pl line 103.

# New Ticket Created by  "AVELING BEN"
# Please include the string:  [perl #53808]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=53808 >


Hi,



I've just received an error message saying:

elseif should be elsif at blah.pl line 103.



What happened to do-what-I-mean?



Perl is usually pretty forgiving.  In this case, it knows that I should
have typed elsif, so why does it care that I typed elseif?  Why not just
treat it as if I'd typed elsif?



Regards, Ben



--

Ben.Aveling@alcatel-lucent.com.au

Ben (> ):
>  I've just received an error message saying:
>
>  elseif should be elsif at blah.pl line 103.
>
>
>
>  What happened to do-what-I-mean?
>
>
>
>  Perl is usually pretty forgiving.  In this case, it knows that I should
>  have typed elsif, so why does it care that I typed elseif?  Why not just
>  treat it as if I'd typed elsif?

I'm not sure laxity among keywords would really be a feature.
Correctly spelled, it's "elsif" in Perl, so why allow misspellings?

Allowing "elseif" would constitute having two reserved words pulling
the weight of one. Similarly allowing "whlie", "wehn" and "ulness"
just because it reduces compilation errors, is a bad idea.

// Carl

On 2008 May 7, at 7:21, Carl M=E4sak wrote:

> Ben (> ): 
> I'm not sure laxity among keywords would really be a feature.
> Correctly spelled, it's "elsif" in Perl, so why allow misspellings?

I thought WATFIV proved that this was a really bad idea....

--=20
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH