@TimStone FYI that Swing file chooser bounty expires in four hours or so. If you stopped caring, that's cool, but if you just forgot, this is your reminder.
@PopularDemand I was a little surprised (probably not really the word for it, but) too. The answers were all good-faith, but they weren't actually applicable to the question.
Yeah, I'm still learning the ins and outs of Perl 5. I have a decent understanding, but it still doesn't feel very fluid to me yet. So, Perl 6 is gonna have to wait. :)
There was some language (Haskell?) that let you use operators and functions pretty much interchangeably, so stuff like map(<, (9, 10, 11)) would work. I was a fan
Yeah, what he said. For example, in some languages strings are immutable. When you concatenate a string, ti actually creates a new one, even if you're storing it in the same variable.
I doubt I read even 10% of the posts though. :) Not that I need to read them all. E.g. I have some feeds from (real world, not programming) architecture blogs, which I only read on occasion when I'm in the mood.
Well, as my dad once said about all the projects he has: It's like carrying water with sieves. You gotta run fast and not worry about what falls through.
So, the large number of feeds is a sign of my large variety of interests. I tend to read the security related ones quite regularly. I do need to get the programming ones into the rotation some more. But, the feeds aren't the only source of programming information.
I wrote a Python script for a job interview once. Interviewer said it was the best submission he received. It was the first and last thing I wrote in Python.
people like lambdas because they are more efficient in the backend, because you're using a certain semantic that is designed for speed. The compiler really can make lambdas more efficient.
However, when you write code, 99% of the time you're writing code for other humans.
So you should do it in the long way. And on the off chance that you do optimize for speed (like on a tight inner loop) then you should convert to the lambda only after commenting out (and leaving in place) the existing "long way", with a comment of why and when the lambda was inserted, and that it was for previously profiled bottlenecks
Because, by leaving the old code, you leave what did work, as a record in the sand, for the next wayfarer who has to support that block (which will be you, who will be pissed that he has to maintain a lambda)
I've only seen lambdas done because they were clever, or because they reduced the number of declared functions (which doesn't matter to the callstack, an anonymous function is still a function)
And this, ladies and gentlemen, is why we have different coding styles. ;) Right @LasseVKarlsen?
if it's debug code and won't serve a purpose later (I mean ... really, you need debug code later? it's too complex! refactor!) then remove it. If it's "I did this really impressive thing which may blow up later" then I say leave the old code in. But I agree with Lasse that it's always in the SCM archives. It's totally up to you on your style.
@Trufa remember to always make it more human readable first ;) nobody will complain, even if they call you a n00b. But then you'll get to sound like the grown-up adult not-at-all-a-13-year-old-script-kiddie that code is human readable first, and why do they have to make theirs look so 1337, can they not code "for others" ;) :P
Useful information to be sure, I even bookmarked a couple of those videos, but the post is not fitting for SO, and leaving it up would set a dangerous "counter-precedent" after earlier changes in the rules. So it had to go.
I wanted to give people time to adjust. I need a new avi pic anyways. I might get someone to take one of me tonight. But I really need a haircut first.
Hmm, after I get a haircut I'll post a new avi pic
I rushed out early this morning to get a haircut, thinking I had to be back for a meeting at 10:30. Apparently that meeting was cancelled while I was in the chair.
