Uhhhhh, after I have read the Object Oriented Perl book, I wish that there is some UML modeler that will let me customize the perl OO code generation.. huhu
anyway, my evil perl code is hard to read whether I use the normal or OO style coding, for me, I will need some modeler + good source code documentation + good OO design skill along with the OO Perl skill.. all together to ease my perl life :))
Studying/Exploring/Developing/Finding those tools might be the next step that will highlight the usefulness of studying OO Perl.
In the opposite way, if I can find a good perl development tools that will help me with the source code documentation, it may drag my interesting away from OO Perl (e.g like having Siemen 's EasyCODE for Perl.hu hu)
Infer: knowing OO Perl is not the last thing that I have to study for my perl life :D
*uh, what if LabVIEW or IFAD VDM++ can generate OO Perl code!*
-
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.
|
