auto storage class - infer or RAII?

[Kristian Kilpi]

On Sun, 12 Nov 2006 08:50:51 +0200, Daniel Keep  
<daniel.keep.lists at gmail.com> wrote:
[snip]
> On a related note, I don't suppose I could ask you to take a second look
> at my old proposal on allowing auto objects to be returned from
> functions, could I? :P  It is one of the very, very few things I'd still
> like to see in D 1.0.
>
> <http://www.digitalmars.com/d/archives/digitalmars/D/38329.html>
>
> 	-- Daniel
>

I especially liked the the 'auto members'. It's not uncommon that member  
variables of an object are only used by the object (they are binded  
together forming a compact entity), and they should be destroyed with the  
object. Currently you have to explicitly delete the member variables in  
the object's destructor, right? Sometimes I miss value types. They are  
created and destroyed with the parent object automatically.

And basically you're trying to create value types here? Objects are  
destroyed at the end of scopes, and they are cloned/dublicated in  
assingments. In reference counting the objects themselves are cloned, the  
data is refenced. Well, actually the reference counts must be updated in  
assignments. So, what we actually need for reference counting is an  
ability to override the assignment operators.