philip r brenan

  • Commented on A dream realized
    The opening comments argue that because some people have worked in this area for some time then their "authority" is enough to make the claim that Corinna is valuable. But this is a well known fallacy: If these people...
  • Commented on Perl Weekly Challenge 127: Disjoint Sets and Conflict Intervals
    #!/usr/bin/perl #------------------------------------------------------------------------------- # Are two arrays disjoint ? # Philip R Brenan at appaapps dot com, Appa Apps Ltd Inc., 2021 #------------------------------------------------------------------------------- use warnings FATAL => qw(all); use strict; use Test::More qw(no_plan); sub disjoint($$) {my %a = map {$_=>1}...
  • Commented on Making Taint support optional in Perl
    Likewise we use taint in web applications whose code does not show up on CPAN. If taint were removed in later releases of Perl that would deny us an upgrade path to those releases. If you wish to remove taint...
Subscribe to feed Recent Actions from philip r brenan

  • laurent_r commented on Perl Weekly Challenge 127: Disjoint Sets and Conflict Intervals

    Hi Philip,

    I love both Perl and Raku and do not wish to get into an argument about which language is better. Sure, when you start with a new programming language, you have to spend time to learn it. If you don't want to spend that time on Raku, fair enough, that's a perfectly reasonable argument. I personally very much enjoyed learning Raku and certainly do not regret the time I spent learning it.

  • Damian Conway commented on A dream realized

    I'm a little confused, Philip. You ask me to rewrite the article so that you can "know the compelling reasons why Corinna is so good"...but the article already contains at least six of those:

  • More concise syntax (therefore more readable)
  • More declarative syntax (therefore less boilerplate implementation code required)
  • Less prone to bugs (because more concise and more declarative)
  • Better performance for most method calls
  • Compile-time checking for at least one common type of error
  • Built right into the language, so no need to rely on external modules …
  • Oodler 577 commented on A dream realized

    You're expending some hard won social credit on this endorsement of this latest attempt at POOP. For the sake of Perl, I hope you are hitching yourself to the correct attempt and not in some vain attempt to lend credit to the claim that, "POOP is not the problem, it's just never been implemented properly". Sounds like a familiar claim.

    Subscribe to feed Responses to Comments from philip r brenan

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