Today, according to Seinfeld, is Festivus the Holiday for the rest of us. One of the rituals of Festivus is the Airing of Grievances. It consists of lashing out at others and the world about how one has been disappointed in the past year. In particular, let's lash out at Perl.
Here, I'll start.
Perl, I hate your dereferencing syntax so much.
push @{ $hash->{key} }, 42
Oi what a mess! Why can't you just put autoboxing into the core?
$hash->{key}->push(42)
Is that so hard? Your sister Ruby can do it, why do you have to be such a shlemiel?
Autoboxing,.. eah (Score:1)
I agree the deref syntax is yuk, but I don't know if autoboxing is the answer. I actually think the direction of the pipeline with autoboxing is weird, not to mention the whole "is it returning things or modifying in place" confusion (yes, yes, obviously people would figure that one out, but both options are totally legit, so it is not always obvious which one it should/would/could be). Overall I found autoboxin' [cpan.org] to be kinda un-Perlish myself, I prefer to just meta-program [cpan.org] all that yuk away instead.
- St
Re: (Score:2)
Eenhhhhh. (Score:1)
I don’t see why we’re being forced to write the outer deref. It could be much simpler:
Much nicer than autoboxing, too.
There’s never any more or less of a guarantee that
$hash->{key}will be an array-ref anyway, regardless of which way you write it. There's never any ambiguity there either. The current rule is just arbitrary outgrowth of the prototype brain damage. A better way to approach the problem that prototypes attack would have been to provide a preRe: (Score:2)
lemme see... (Score:2)
Stringifying of references.
Taking strings so seriously that seeing them as characters becomes hard.
Re: (Score:2)
down with "my $self = shift; " (Score:1)
self.pm [cpan.org] helps some but lacks an equivalent of "shift".
Grievance number 2: The large scope of the Perl 6 spec means Perl 6 will take even longer to complete. I would prefer simpler, sooner.
Floating point sucks (Score:1)
Sorting kvetch (Score:1)
Methods (Score:1)
Why is the only difference between methods and functions at the point of call, not the point of declaration?
Ohhh! Don't get me started! (Score:1)
* I have to worry about circular references? WTF! It's not like a decent garbage collection system is exactly cutting edge.
* Having to write use strict/warnings/-T in every damn file
* Source filters, and the deluded folk who think they are as good as Lisp macros
* SUPER being related to the package the method was compiled into. Like that makes sense.
* Depth-first method resolution by default
* The evil mushing together of namespaces and classes
* Packaging up a whole bunch of stu
Re: (Score:1)
Re: (Score:1)
* Packaging up a whole bunch of stuff for deployment by non-Perl gurus is just too damn hard
Amen.