Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!apple!snorkelwacker!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!sequent!mntgfx!plogan
From: plogan@mentor.com (Patrick Logan)
Newsgroups: comp.lang.eiffel
Subject: Re: What happens when you're gone and forgotten?
Message-ID: <1990Mar20.174709.6521@mentor.com>
Date: 20 Mar 90 17:47:09 GMT
References: <1586@xyzzy.UUCP> <6025@star.cs.vu.nl>
Organization: engr
Lines: 20
In-reply-to: jos@cs.vu.nl's message of 19 Mar 90 14:48:13 GMT

In article <6025@star.cs.vu.nl> jos@cs.vu.nl (Jos Warmer) writes:
   To get the behaviour you desire, inherit from class MEMORY and
   redefine the `dispose' function.
   --
				    Jos Warmer
				    jos@cs.vu.nl
				    ...uunet!mcvax!cs.vu.nl!jos

Here's what I was missing from my previous posting, i.e. multiple
inheritance so that the "dispose" procedure is only called on objects
that need to use it.

Does Eiffel use this in the window system classes to protect X's C
allocated structures?

Where (else) does Eiffel use this? Is it always to deallocate C data?
-- 
Patrick Logan  uunet!mntgfx!plogan | 
Mentor Graphics Corporation        | 
Beaverton, Oregon 97005-7191   	   |