This is to say that I know that it's not an all or nothing decision to use OO techniques, but I feel like, where we are using it, we're not taking full advantage of its capacities. I came to this conclusion while reading through Fowlers Refactoring and as I'm reading through the "Bad Smells in Code" chapter I'm seeing a lot of things that we're doing.
As we've discussed both here and elsewhere quite frequently and also very recently, it's officially OK in Perl to speak only a subset of the language, and OO makes no difference. Of course just as in all those other respects, this is not an excuse for not improving one's knowledge of the language if wanting to use it regularly. Code smell is a whole another story, and you should actively work to remove it: learning what's wrong with some code constructs and see what people do instead, may be a good starting point for your improved learning of the OO dialect of Perl.
-
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.
|