Re: .NET approach

On Fri, 01 June 2001, "Steve Richter" wrote:

> 
> Full objects encapsulate data and member functions.  Using this definition,
> 

Steve:

Could you elaborate on this? In particular, if I create (instantiate or 
whatever) such a "full" object and then examine it directly with some fancy 
memory display utility, will I actually see a block of memory that contains the 
machine instructions that implement the methods along with the data? If I 
create a 2nd "full" object, would I see a 2nd memory block with another copy of 
the machine instructions?

Trying to determine the actual difference between "full" and "half" as opposed 
to a difference in the visible programmer or user interfaces. I've seen strong 
examples of how some objects are handled by the OS in OS/400, OS/2 Warp and 
Win95/NT/etc.; but I'm interested in your specific reference to "full" objects.

Tom Liotta

___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/




+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---