Except you have to create a convoluted mess of tying a variable and returning it in a way that is both hard to read and hard to maintain, at the dubious benefit of having sugar that is not socially acceptable *ANYWAY* in perl today.

What is the point of your discussion? Are you proposing to revise the currently unversally accepted style? Because Perl 6 is already doing that and it will look like you want it to look, except it won't be insane.

If you are trying to fix the accessor code smell (Which is moot in my opinion - accessors are necessary for storing data in a data oriented culture like perl whether the smalltalk heads like it or not) by abusing weird perl features is IMHO not going to give you any less code smell, but actually more (IntentionNotAlgorithm, KeepItSimpleStupid, YouAren'tGonnaNeedIt, FeatureCreep).

Punchline: you're proposing to simplify by making it more complex. That's wrong. I think that this is MentalMasturbation.

---

---

• 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 How to display code and escape characters are good places to start.