user-pic

Ivan Paponov

  • About: Yet Another Perl Blogger
  • Commented on Workflow, part 3
    Thanks for the comments, John. I'm totally agree about private methods. But I think that the right way to solve this little issue, it to create patch with public wrapper to that private method, and submit it to cpan :)...
  • Commented on Perl's "readability"
    It looks like accent problem for me. Take couple of people, english speakers. Let's assume that one has cockney accent, and other - some asian english accent. They both speak english, but do you think they will understand each other?...
  • Posted Workflow, part 3 to Ivan Paponov

    I presented OOP approach for solving workflow tasks in my previous post. I'm gonna write about ="http://search.cpan…

  • Posted Workflow and Perl, part 2 to Ivan Paponov

    Let's make some code.

    Let's use quite simple straightforward approach, and then modify it with some design patterns.

    General idea:

  • Posted Workflow and Perl, part 1 to Ivan Paponov

    I'd like to start series of posts related to workflow, workflow management systems and of course Perl. Workflows seems to be quite “hot” topic in all that world of enterprise software for the last ~5 years.

    First, let's figure out what workflow is, why we should care and how Perl can …

Subscribe to feed Recent Actions from Ivan Paponov

  • Dody Suria Wijaya commented on Perl's "readability"

    I don't fully agree with you Randall. What I found is that in practice, especially short utilities and in unix-related scripting, Perl is a lot easy to make reading difficult. There's a culture of encouraging writing hackish or 1-time use perl program using as short operators as possible, like 1 character symbol. It might conveys "dense" meaning, but damn it overwhelm readers. Of course those utilities sometimes age much longer and survive through the next unlucky maintainers.

    This is probably less of an issue with language, and more of the writer itself trying to save time typing a…

  • Naveed Massjouni commented on Perl's "readability"

    Most of the people who say perl is unreadable either never learned perl or have never seen modern perl. The flexibility and power of perl that makes it possible to write obfuscated code also makes it possible to write code that is more readable and elegant than other languages that are more restrictive. And now for some code! Here is one of my favorite modules http://p3rl.org/Test::Class::Sugar , a DSL for writing tests:

    
    

    use Test::Class::Sugar;
    testclass exercises Foo {
    test that Foo knows his brother {

  • Naveed Massjouni commented on Perl's "readability"

    Sorry for the extra newlines in my last post. I put my code example inside 'pre' tags, and it seems to render it with an extra newline for each line. If someone knows a better way to post code samples, then please share :)

  • mrstlee commented on Perl's "readability"

    Is readability:
    or
    b) A qualitative assessment of how easy the content of the document is to comprehend (however you assess that)
    or
    mixture of the 2
    or
    other?


    I find English translations of "Tractatus" easy to parse - but hard to comprehend. Enid Blyton's Famous Five adventures don't pose me the same problems, although ethically I struggle with the notion of the parents allowing 4 children and a dog to spend 2 weeks unsupervised in a remote lighthouse.

  • pyrimidine commented on Workflow, part 3

    Very good set of posts, was hoping to see the next in your series!

Subscribe to feed Responses to Comments from Ivan Paponov

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.