I tried to contribute on this list but it seems we've coalesced downto Tom
and a handful of others. No one else has a voice.
I have nothing but respect for Tom, Nathan, et al, but its no longer my idea
of a community - more like a faction. I'm getting more into PHP now and
less into Perl, onl
These would be perlish, nice, terse, succint, and economical:
my ($a, $b, $c) = 0;
@h(@colours)='red';
($i, $i, $k) += 2;
@nums = 10 * @nums;
.
.
.
Ed
_
Get Your Private, Fre
Since there were no objections to cleaning up the error messages on
unbalanced parens and braces, can we RFC that request?
-Ed
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information
use diagnostics;
my $i=1;
print 'hi' if ($i=1;
running this with perl -wc (v 5.004, unix), I get
perl -wc x.pl
syntax error at x.pl line 3, near "1;"
x.pl had compilation errors (#1)
(F) The final summary message when a perl -c fails.
Uncaught exception from user code:
I really like
(do something) if (something is TRUE);
as opposed to
if (something is TRUE) {do something}
Just personal taste I guess, but to me the former is a nice Perlism.
So what about
(do something) foreach (some list);
i.e.
print foreach (@l);
as opposed to
foreach (@l)
Shoot chop. and chomp. Unless you add unchop and unchomp. Parity issue. Like
a language with YES and no NO.
Just kill then both.
>From: Bryan C. Warnock <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: Michael G Schwern <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>Subject: Re: RFC 195 (v1) Ret
The fact that something can be accomplished in Perl doesn't necessarily mean
its the best or most desirable way to do it. I respect the programming
abilities, but
grep { ref($a) eq ref($b) } @b)
is far less intuitive than the proposal. I could perhaps dig into my distant
memory and explain
Duck & cover Nate- I sugested that weeks ago and the flames are just dying
down in my mailbox..
It'll be an interesting experiement in "community behavior" however. If your
proposal is widely acclaimed or even seriously considered, while mine was
summarily dismissed, then it may be safe to ass
Hey Raptor et al:
Wow you did some homework! Nice ideas, but the consensus seems to be "roll
your own". I've noted that opertors working on arrays are generally
discouraged in favor of scalar ops in these discussions, so for example your
(min,max) (ceiling, floor) are coded thousands of times
Making 0 the first element makes as much sense as 1- just a convention.
However there is precedence for letting the user decide. Does anyone else
remember
)ORIGIN 1
? So we establish a var $something=n where n is the array origin.
I don't think I'd ever use it personally, having been a c "k
Having just coded some more perl resplendent with this syntax:
$in{pmonth}=$usr{paidon};
$in{pmonth}=~s/^.+([A-Za-z]{3,3}).+$/$1/;
once again I'll suggest (then I quit)
$in{pmonth}=~s/^.+([A-Za-z]{3,3}).+$/$1/,$in{paidon};
is a LOT nicer, and more Perlish (see split) way of doing this. I'
hashes and regexes, and the scripting aspect (no explicit, seperate compile
step).
Its not the ONLY language with these aspects, but its the only one I know of
with ALL of them. Also I like the feeling of community and in some respect,
rebellion.
Anyhow those are what distinguish Perl for me.
Excellent idea- anything to get to production faster!
But don't {} or {1} sort of do the same thing?
>From: Larry Wall <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: ... as a term
>Date: Mon, 21 Aug 2000 09:09:01 -0700 (PDT)
>
>Randal L. Schwartz writes:
>: if ($a == $b) { ... }
Is eq needed? Can't == be used for either context?
$a == 'cat'
is readily distinguishable from
$a == 2;
so the compiler should be able to determine context.
Get Your Private, Free E-mail from MSN Hotmail at http://
14 matches
Mail list logo
