Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

I’m a lumberjack programmer and I’m okay 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I do think closures are hard for many people to understand, based on the mistakes I see people make in Perl with them. However, Java inner classes are pretty awful too, possibly worse, and adding closures should not have any effect on people who don't choose to use them.

    Probably the most reasonable argument to not put closures in Java is that Java is all about OO and closures are a different paradigm. If he argued that, I'd have more sympathy.
    • I do think closures are hard for many people to understand, based on the mistakes I see people make in Perl with them.

      I think it really depends on what you're used to and how you're taught. I've seen Lisp/Prolog coders having just as much trouble getting their heads around the OO approach. Closure style HOP code isn't harder - it's just sufficiently different that you actually have to learn it. (IMHO anyway :-)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.