use Perl

• chaining (Score:2)

  by TeeJay (2309)

  ..but if you chain operators you aren't checking for failure :)

  --
  
  @JAPH = qw(Hacker Perl Another Just);
  print reverse @JAPH;
  • Re:chaining (Score:1)

    by runrig (3385)

    That is not necessarily true. You can easily eval the whole thing, and die with, e.g. "'Some value' illegal value for property 'bar'". Though I'm not making an argument about whether or not chaining setters is a good practice.
  • Re:chaining (Score:1)

    by TheNomad (7014)

    Good point!

    But it sort of sounds like an argument for design by contract.

    Oh btw, thanks to the two so far who have left a comments on my first over post! :)
  • Re:chaining (Score:1)

    by Alias (5735)

    If you are chaining methods you have to do error via exceptions.
• Chaining Accessors (Score:2)

  by davorg (18)

  I think you want Class::Accessor::Chained [cpan.org].
  • Re:Chaining Accessors (Score:1)

    by TheNomad (7014)

    Thanks perfect!

    I haven't made up my mind whether accessors that return the object are such a good idea. Say, for example, you have some basic code:

    package DoStuff;
    .... code to make accessors goes here. We have get_foo and set_foo.
    
    sub make_foo_value {
    $self = shift;
    $self->set_foo(rand)
    
    }
    
    package main;
    
    my $stuff = DoStuff->new;
    $stuff->make_foo_value;

    What should make_foo_value return? If it returns $self, then you need to go:

    print $stuff->make_foo_value->get_foo;

    On the other hand, if