Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!tank!ncar!ames!hc!pprg.unm.edu!unmvax!gatech!emory!dtscp1!joel
From: joel@dtscp1.UUCP (Joel Rives)
Newsgroups: comp.lang.c++
Subject: Re: Generating temporaries
Message-ID: <617@dtscp1.UUCP>
Date: 6 Apr 89 06:10:30 GMT
References: <7.UUL1.2#261@persoft.UUCP> <SCP.89Apr4162957@raven.lanl.gov> <1531@wasatch.utah.edu>
Reply-To: joel@dtscp1.UUCP (Joel Rives)
Organization: Digital Transmission Systems (a subsidiary of DCA), Duluth, GA
Lines: 18

In article <1531@wasatch.utah.edu> mecklen%gr.utah.edu.UUCP@wasatch.utah.edu (Robert Mecklenburg) writes:
>
>The disadvantages are:
>
>	1.  breaks easily if programmer holds on to a temporary too
>	    long, the circular queue will eventually trash his
>	    temporary with no warning;
>	2.  to be reasonably safe the pool must be reasonably large
>	    (we use MAX_POINT_POOL = 64).
>
>Comments?

Though i admit your method is clever, the primary disadvantage that you 
mention above is one which i -- as a developer -- would not want to live
with. It introduces the possibility of a side-effect which could (and 
probably would) create hard to track down bugs.

Joel