sheesh.
fucking spamassassin and their fucking memory-hog code.
SCALAR EACH IS YOUR FRIEND, DIPSHIT.
sheesh. I did *not* need to be optimizing code written by people I've never met. (EDIT: though technically, in my mind, addressing 'out of memory' errors that crop up under normal usage isn't optimizing anymore; it's debugginging.)
SCALAR EACH IS YOUR FRIEND, DIPSHIT.
sheesh. I did *not* need to be optimizing code written by people I've never met. (EDIT: though technically, in my mind, addressing 'out of memory' errors that crop up under normal usage isn't optimizing anymore; it's debugginging.)
no subject
You wouldn't want the SpamAssassin people to write bad Perl, now, would you?
*innocent*
no subject
ask me again after I've spent two weeks upgrading software so I can get my installation running a new enough version that the SA folks will speak to me.
no subject
I will not laugh at my friend's misfortune.
I will not laugh at my friend's misfortune.
*giggle*
Well, at least I didn't laugh.
it gets worse...
Do you know what that led to?
I spent today helping Z get an NFS server set up on his windows server.
I don't wanna talk about it.
(*thwwwwwwpt!*)
Re: it gets worse...
Re: it gets worse...
Still took far too long, but, well, it's NFS, and NFS is scary all by itself!
Re: it gets worse...
no subject
Although it would be nice if Perl could recognize that, in for $x (keys %y) { foobar $x }, the array value of that keys %y is never actually used as such and so doesn't need to be constructed. I can understand if static analysis would be too much, but surely there's already enough runtime magic strewn about that this kind of thing can be tossed in. (For example, having while ($x = each %y) { foobar $x } not halt when the key is "0" or "".)
On the other hand, at what point does Perl stop being a scripting language and start being a DB query planner?
no subject
for $x (keys %y) { ... }
then we should be able to do it for
for $x (grep(/pattern/,keys %y)) { ... }
and, and, and!
(people just like me are why perl is the swiss army chainsaw.)
no subject
(Bigger chainsaw!!!)
no subject
In a lot of cases, you want to halt on false-evaluating values, and it's relatively simple to add a C<defined> operator.
no subject
I hate that one, and it seems that *everyone* and their brother does it.