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