comment on

I found this whole thread interesting. When i read the title I thought "yep, I agree with that" but then on reading closer it wasnt even what I was thinking at all! :-) What I thought you meant was all those aweful sub like

sub get_foo {
  my $self=shift;
  return $self->{foo};
}
[download]

and its correspondingly ugly set_foo. If you had been talking about those being evil then i would agree. :-) Perl offers fancier and IMO more intuitive ways to do things:

sub foo {
  my $self=shift;
  if (@_) {
    $self->{foo}=shift;
    return $self;
  } else {
    return $self->{foo}
  }
}
[download]

(or a variant thereof, you can golf it down nicely. :-)

---
demerphq

_{First they ignore you, then they laugh at you, then they fight you, then you win.

-- Gandhi}

In reply to Re: Why get() and set() accessor methods are evil by demerphq
in thread Why get() and set() accessor methods are evil by synistar

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks