Re: (beep) as string
Re: (beep) as string
- Subject: Re: (beep) as string
- From: "John W. Baxter" <email@hidden>
- Date: Sat, 22 Nov 2003 13:26:10 -0800
- Envelope-to: email@hidden
On 11/18/2003 12:56, "Christopher Nebel" <email@hidden> wrote:
>
However, I happen to agree with the "buggy" behavior. I expect to
>
change AppleScript at some point to be not so fussy about "undefined"
>
values -- Perl works this way, and it seems to work well for them.
Well, it works OK for Perl now. But largely because of the addition of
use warnings AKA -w
use strict
many Perl versions ago.
Which together get rid of many of the "accidental" uses of undefined
things...ie bugs.
In other words, please don't go overboard on "improving" the behaviors
around undefined values. There are instances which are probably OK to
improve.
[john@Zeus tmp]$cat t.pl
$foo="something";
print "Why isn't there something between the pipes |$foor|?\n";
[john@Zeus tmp]$perl t.pl
Why isn't there something between the pipes ||?
vs
[john@Zeus tmp]$cat t.pl
use warnings;
$foo="something";
print "Why isn't there something between the pipes |$foor|?\n";
[john@Zeus tmp]$perl t.pl
Name "main::foo" used only once: possible typo at t.pl line 3.
Name "main::foor" used only once: possible typo at t.pl line 4.
Use of uninitialized value in concatenation (.) or string at t.pl line 4.
Why isn't there something between the pipes ||?
vs what I might have meant:
[john@Zeus tmp]$cat t.pl
use warnings;
$foo="something";
print "Why isn't there something between the pipes |$foo|?\n";
[john@Zeus tmp]$perl t.pl
Why isn't there something between the pipes |something|?
--John
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.