🚀 go-pugleaf

In article <1emr1oINNas3@iskut.ucs.ubc.ca>, rawsthor@unixg.ubc.ca (Peter
Rawsthorne) wrote:
> My present approach is to create a class hierarchy separate 
> from the existing MacApp TObject library, called CDBMSObject.
> This seems to make sense given that SQL calls do not lend
> themselves to being inheritable.

This feels weird. Here I'm stating that try to avoid TObject 
base class use, and I'm a MacApp support engineer. Anyway,
the main reason is:
* You are locking to features in TObject that are hard to 
re-port to Bedrock, Interviews, Garnet, Alar, whatever new
frameworks out there

In other words cloning and other TObject specific features
will be hard to reimplement. Now, if you are unsure about
memory handling, use HandleObjects, or look at SLM that
provides memory pools and GetObjectByName style object
creation. 

Another design idea is to try to avoid any dependencies 
whatsoever and write class libraries that have a minimal
interface to the underlying OS. This is my motto nowadays.
If you do a nice design you might be able to port your SQL
classes to various other platforms. 

Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.