Re^3: How to understand chapter 6 of Higher Order Perl?

in reply to Re^2: How to understand chapter 6 of Higher Order Perl?
in thread How to understand chapter 6 of Higher Order Perl?

Nah, I actually understand what it does (which is nothing useful). I just find it very annoying.

I don't disagree with you.

That's not the real problem, of course. The problem is that I need some kind of tool or something to track all these function calls. So far I'm doing it manually, and that's kind of difficult when there is stuff like ... I find it kind of unreadable even without promise.

Again, I don't disagree. I call it obfuscation through over-encapsulation.

The misguided attempt to gloss over moderately "difficult" perl syntax with myriad small, trivial named subroutines or methods. All it does is obscure the underlying algorithm; complicate maintenance and debugging; and throw performance to the dogs of dogma.

This is far simpler, clearer and way more efficient.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: How to understand chapter 6 of Higher Order Perl?

Replies are listed 'Best First'.
Re^4: How to understand chapter 6 of Higher Order Perl? by Anonymous Monk on Mar 13, 2014 at 11:31 UTC
This is far simpler, clearer and more efficient You're right. And "syntax with myriad small ... subroutines" is not good for me at all. Especially when many of these subroutines tell that they're called __ANON__. I'll do as the fellow Anonimous Monk recommended. Thanks everyone.	[reply]

In Section Seekers of Perl Wisdom