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


in reply to Re^2: Extract Block Of Text From Log
in thread Extract Block Of Text From Log

I fully support your argument. I just like to write easy-to-read easy-to-port examples.

When you write stuff that might still have to be supported in a couple of decades, then making it easy to read and understand is much more important than making it "nice and fast and only understandable by perlmonks" ;-)

perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'

Replies are listed 'Best First'.
Re^4: Extract Block Of Text From Log
by LanX (Saint) on Nov 23, 2018 at 10:22 UTC
    > only understandable by perlmonks" ;-)

    I disagree because state-machines need a lot of documentations and flip/flop is well documented in perldoc.

    At worst you'll just need to add a link in the comments.

    > just like to write easy-to-read easy-to-port examples.

    So consequently you use goto instead of loop constructs, to keep it easily portable to assembler? ;-)

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

[reply]

      I very rarely use goto, but there are a few cases where it is the correct function to use.

      perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'
[reply]
[d/l]

In Section Seekers of Perl Wisdom