Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!ncar!dinl!schwartz
From: schwartz@dinl.uucp (Michael Schwartz)
Newsgroups: comp.lang.c++
Subject: Re: Support for movable objects in C++
Message-ID: <1472@dinl.mmc.UUCP>
Date: 4 Oct 89 20:24:59 GMT
References: <1989Sep30.051559.20644@polyslo.CalPoly.EDU> <6590275@hplsla.HP.COM> <1989Oct4.161939.12442@polyslo.CalPoly.EDU>
Reply-To: schwartz@dinl.UUCP (Michael Schwartz)
Distribution: usa
Organization: Martin Marietta I&CS, Denver CO.
Lines: 22

I may be missing something in this discussion, but isn't this exactly
the problem that Glockenspeil's (public domain) Containers abstraction
is supposed to solve?

One sets the file allocater to use whatever method one wishes (default
is the stack (not movable), and doesn't worry about it after that.  It
is the 'lock object's job to lock the object down to a known address
when accessing it, otherwise the object can float freely.

Correctly, according to their documentation, this takes a long while to
get used to (about 5 solid nights of work for me).  The documentation is
a bit lean.  However, it does work nicely.

Please don't flame me if I missed the point of discussion.
-- 
-----------------------
schwartz%looney@mmc.com    "Expect everything ... 
mschwartz@mmc.com                   and the unexpected never happens." 
ncar!dinl!schwartz                               --the phantom tollbooth

DISCLAIMER:  The opinions expressesed are not necessarily those of my 
	     employer or myself.