|Procedural code often tends to separate data and the processes applied to that data. OO tends to do the opposite.
Often procedural code is written in pseudo-OO style. I.e when you see a lot of subs with signatures like
sub do1($datastructure1, ..)
sub do2($datastructure1, ..)
sub do3($datastructure1, ..)
sub do4($datastructure2, ..)
sub do5($datastructure2, ..)
sub do6($datastructure2, ..)
It is relatively easily to convert to OO code. You put all subs which work on same data structures in same classes and then you apply various refactorings(like this
) to get more ideomatic OO code.
Ilya Martynov, email@example.com
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support
UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||