NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Syntax (Score:1)
Is uglier than (I agree):
And
Is uglier than (meh):
Reference handling is one of the few things I really don't like about Perl. In a high level language like Perl, you shouldn't have to worry about what's a reference what isn't (most of the time). It goes against DWIM.
He also complains about having to change the prefix on the array to access the individual element.
Re: (Score:1)
Honestly, I don't see a problem with the references. You can always write $foo->[3] to dereference the array. And I really don't agree that references and non-references should be interchangable. Since non-refs and refs behave differently, you _have_ to differentiate them. Otherwise this would just scream "action at a distance" to me.
I can however, understand why non-Perl people have problems with the changing sigils. Because they aren't used to it. Personally, I like it, but I can see why it was decid
Ordinary morality is for ordinary people. -- Aleister Crowley
Dereferencing (was: Syntax) (Score:1)
Reply to This
Parent
Re: (Score:1)
What’s really annoying is that there’s not even any reason for the prototype on
keys(nor, really, on most other functions). Even ifkeys $foowill blow up at compile time,keys %$foowon’t – but that doesn’t mean the reference is a hash ref. The only reason forkeysto have a prototype is because of how the parser works; a mere artefact.Context-sensitive sigils worked for Perl 4 because it doesn’t have references; in Perl 5 they are a pointless wart.