Re: [Slashcode-development] Oracle Port Progress, April 19: Inheritance Tax

[Chris N. <pu...@po...>]

At 00:15 -0500 2001.04.20, Stephen Clouse wrote:
>reason.  I dug up this comment in Slash::Apache::User:
>
>#Ok, this solves the annoying issue of not having true OOP in perl

Well, that is one man's opinion, anyway.  :-)

># You can comment this out if you want if you only use one database type
># long term, it might be nice to create new classes for each slashdb
># object, and set @ISA for each class, or make each other class inherit
># from Slash::DB instead of vice versa ...
>
>Perl's interface inheritance is definitely a "bottom-up" approach along the
>lines of Eiffel, so trying to force the downward inheritance into Slash::DB
>itself doesn't work very well.  So today I fixed that, flipping the current
>"top-down" model over.  IMO Slash::DB just got a hell of a lot simpler -- all

Well, we have been considering ways to change it anyway.  I am not sure
what you mean when you describe how you changes it though.  That is:


>it
>does is figures out the correct class name, loads the necessary driver module,
>and then blesses the initial hash into that class instead of Slash::DB.  The
>onus for proper inheritance is now placed on the database driver module, which
>is probably a Good Thing.  I've already patched all the existing drivers and

How does the database driver module determine inheritance?  Do you mean
that now you get back a Slash::DB::MySQL object instead of a Slash::DB
object?


>I've also tightened up Slash::DB::Utility some more, breaking out select
>statement generation into an independent function, as well as reusing
>some of the sql functions inside the sql functions when possible.  This
>eliminates copious amounts of redundancy in the sqlSelect* routines.
>MySQL code
>continues to work in its original form (I haven't gotten around to
>modifying any
>of it yet), so I'd have to say the extended interface has proven itself clean
>and backwards-compatible.

Again, I need patches.  I cannot comment on the usability of the code until
I see it.  And if you want it in Slash 2.0, it needs to be done ASAP.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/