comment on

This argument extrapolated leads to "variables considered harmful" and is total bollocks. Indeed it can be problematic when you can assign arbitrary values to variables, with no validation whatsoever. That's also the basis of many programming languages, and programming would be very impractical without this.

An object property is just a variable attached to the object. It's insane to treat it much differently.

While value validation is a useful addition, it's not necessary. Many a time value validation means you're limited by the API designer's creativity, and gets in the way.

Until we have Perl 6, I prefer to write code that isn't picky. Having tolerant code is not so bad as it looks, especially if you consider that making something non-picky afterwards is hard in Perl 5.

In reply to Re^5: Juerd, the overlooked (ORMs, Webapps) by Juerd
in thread Juerd, the overlooked (ORMs, Webapps) by metaperl

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks