Heavy OO design, what's the PHP-specifc downsides?

G'day, I'm in the throes of developing a system for use within my university section. Being a child of the C++ background I am edgey to put good OO design to work in my application. However I am wary that I really don't yet know this language or it's limitations, and would hate to have a great system in concept and on paper only to find out that PHP doesn't scale well to it. For example: I almost always derive all my objects from a single parent (cplOBJECT) I use this for some basic run-time type checking, and as an abstract base class for the interfaces to the error and debug classes. That's all well and good, but since PHP is scripted I might be asking too much especially for simple basic classes. My little devil's advocate on my shoulder however can't help but see the usefulness in having a common error/debug interface to efficiently use information hiding. I know alot of libraries (probably all, but I won't say that ;) use the method I'm hassling you all about (like phplib, prometheus...) I just want to hear it in near real-time from yourselves as to advantages/disadvantages. So please PHP-crew, offer any and all advice, Thanx! -------------------------------------------------------------------------- Matthew M. Boulter email: mboulter@uq.net.au Conceptua Media Developments mobile: 0414-912-501 (for the University of Queensland) --------------------------------------------------------------------------