> > so far all my libs (well there ain't much ) are all OO pm files.
>
> There is what I would call the 'dataLess' OO solution,
> what is known as a 'utility class' - where one has only
> a stack of methods that one wishes to have in a 'nameSpaceSafe'
> environment - so that you know that
>
> my $dataLessObjectInstance = FOO::BAR->new();
>
> $dataLessObjectInstance->print("die KMT Puppet");
>
> now you know that the 'print' function you have in
> that FOO::BAR will not compete with the 'print' function
> that comes with perl.... nor do you have to worry about
> the problems of 'overloading' the 'print()' method that
> was the standard....
exactly. IMO this is where the advanage is. In my experience, it is easier
to "protect" name spaces and "read only" attributes.
>
> I think the easiest path most folks take is:
>
> a) I wrote a script
> b) I learned how to put functions in it
> c) I started cutting and pasting the same functions around
> d) I built a perl library of them
> e) I built a perl module of them so I could use the
> autoloader solution and the %EXPORT_TAGS reference
> so as to load only those that I wanted...
> .....
that was pretty much my path !
>
> My still underFinished discussion is at:
>
>
> http://www.wetware.com/drieux/CS/lang/Perl/PM/OO_v_Procedural.html
eagerly awaiting the finished product !
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
