From: Justin Johnson Date: 2002-08-29T19:32:30+09:00 Subject: Re: Temporary VALUE Needs to Be Protected? It sounds like your talking about smart ptr's. I initially tried this but I believe there would be significant overheads throughout the system. After a lot of research I came to the conclusion that using the stack and playing conservative is the best way to go. -- Justin Johnson "Mauricio Fern�ndez" wrote in message news:20020829001707.GC27149@kodos... > That's what I thought, we just have to avoid alloca when the GC is about > to do its job. > > If Ruby were interfaced with C++ we could have a special ValueReference > type which would (un)register the pointer as needed, so that a full > stack marking wouldn't be needed. > > -- > _ _ > | |__ __ _| |_ ___ _ __ ___ __ _ _ __ > | '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ > | |_) | (_| | |_\__ \ | | | | | (_| | | | | > |_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_| > Running Debian GNU/Linux Sid (unstable) > batsman dot geo at yahoo dot com > > There are 3 kinds of people: those who can count & those who can't. > -- Unknown source >