OOP_(re)

Mon, 26 May 1997 14:29:38 +0100 (BST)

Hi all,

I have been following the discussion on Objects with interest.
I would just like to note a number of things;

The TObject type as I implemented it in OBJECTS.PAS has
a number of fields;
	"Parent" and "Child" (each declared as a "pObject")
	"Handle" and "SelfID" (each declared as an Integer)
	"Name" (declared as a String[64])
	"SelfPtr" (private field declared as a "pObject")

At the moment, "Parent" and "Child" do nothing, and "Handle" is
for projected future use (for handles to windowed objects - Win32, etc).

"SelfID" is an integer which holds a unique numeric ID for each 
living TObject descendant.

Can we make TObject automatically become the ancestor of each
Object type (i.e., any object which is just defined as "Object")?;
 if so, is this desirable?; if so, can this solve any of the current 
problems with Streams and stuff?

I would have thought that some of the fields declared in TObject could
be put to better use than I have done so far - and that more fields could
be added to TObject, to cater for other things (i.e., if TObject will become
the ultimate ancestor of all Object types).

Any views?

Best regards, The Chief 
Dr Abimbola A. Olowofoyeku (The African Chief, and the Great Elephant)
Author of:  Chief's Installer Pro v3.50 for Win16 and Win32.
Homepage:  http://ourworld.compuserve.com/homepages/African_Chief/
E-mail: laa12@cc.keele.ac.uk


The African Chief (laa12@cc.keele.ac.uk)