comment on

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, ..)
[download]

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, this and this) to get more ideomatic OO code.

--
Ilya Martynov, ilya@iponweb.net
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

In reply to Re: Re: perl OO - to use or not to use by IlyaM
in thread perl OO - to use or not to use by kiat

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.


Keep It Simple, Stupid
	PerlMonks