I do this sometimes. Usually when I want private data and the object to behave in public like its underlying blessed type (eg, keys %$obj). This can be more useful than having special key prefixes or other nonsense - but by Software Engineering standards its pretty poor form. Good for quick n' dirty stuff though ;-)
Interesting. It doesn't seem to me so atrocious after all. Fortunately perl is flexible enough that you can decide what is good and what is evil depending on the problem at hand in each particular situation.
The problem is that experienced hackers do know when they're doing something that is potentially Bad(TM), and they do on purpose - because they know what they're doing, while occasionally you can see newbies using the same techniques in a totally uninformed matter, which contributes to the spreading of bad programming techniques - what that sometimes in turn contributes to give Perl a bad name...
-
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.
|
