use Perl

• storm of protest (Score:1)

  by davebaird (5885)

  Not a fan of this change. What's wrong with saying $foo->require or die $@; That's not too much to type. It breaks this kind of useful idiom: $this->require or $that->require or die "No alternatives found: $@"; and it breaks this kind of portability even more

  if ( $better->require )
  {
     $better->frobnicate;
  }
  else
  {
      $default->frobnicate;
  }

  It also makes it difficult to write a custom error message - I have to wrap the call in an eval, and so we're back where we starte
  • Re:storm of protest (Score:1)

    by rjbs (4671)

    I have to wrap the call in an eval, and so we're back where we started before UNIVERSAL::require.

    
    No we're not. Now you're wrapping it in eval{}, not in eval "". That's a big win.

    --
    rjbs
    • Re:storm of protest (Score:1)

      by davebaird (5885) on 2005.10.02 9:59 (#43650) Homepage

      I'd argue that's a small win. We're talking about a single call, like eval { $fooo->require }. The only win here is if we declared $foo, not $fooo. eval { $foo->reqiure } is still a runtime error.

      Reply to This

      Parent