http://qs321.pair.com?node_id=1030091


in reply to Re^7: RFC: Simulating Ruby's "yield" and "blocks" in Perl
in thread RFC: Simulating Ruby's "yield" and "blocks" in Perl

No, you're still ignoring the answers I already gave.

It's a meditation about using Perl as (partial) DSL for Ruby.

Again, the benefit of a shorter syntax is better understandable within a Ruby context, where passing callbacks is integral part of the language.

Mastering this technique in Perl takes much longer because a beginner has to understand prototypes and coderefs.¹ Furthermore it's inconsistent in Perl because you can't use prototypes on methods.

And I already admitted that I wouldn't use this implementation in Perl.²

Finally, debating about "beauty" of syntax is in the eye of the beholder, so lets agree that we disagree.³

Cheers Rolf

( addicted to the Perl Programming Language)

¹) Personally, it took me years before I started to hack Perl in this way. Ruby people have to learn it from the start.

²) Could this be the reason I didn't post it under CUFP? Surprise!

³) And I don't like your inquisitory attitude to fight everything you don't understand in mosnter threads.

  • Comment on Re^8: RFC: Simulating Ruby's "yield" and "blocks" in Perl

Replies are listed 'Best First'.
Re^9: RFC: Simulating Ruby's "yield" and "blocks" in Perl
by BrowserUk (Patriarch) on Apr 23, 2013 at 15:33 UTC
    And I don't like your inquisitory attitude to fight everything you don't understand in mosnter threads.

    You post a Request For Comment; and then refuse to answer questions?

    If the thread has become a "mosnter", its because you're *still* dodging the obvious questions.


    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.