From: "Mauricio Fernández" Date: 2002-10-24T22:40:35+09:00 Subject: Re: Things That Newcomers to Ruby Should Know (10/16/02) On Thu, Oct 24, 2002 at 10:22:53PM +0900, William Djaja Tjokroaminata wrote: > Mauricio Fern?ndez wrote: > > > Writing extensions is always quite unsafe, so we're already trusting the > > developer not to bomb Ruby's internals from C. It would be easy to add > > something like rb_set_dirty_bit() so things don't get nasty when > > keeping several references in C. > > Hi batsman, > > I think there are already existing Ruby applications/library/extensions > that are written in part in C (that have references to Ruby objects). I > don't think we can expect all of them to add rb_set_dirty_bit(). How many do need several references to the same string from the C side? If the number is high enough (ie, > a couple of them) doing this would be pointless :-( Bah, just have to find another thing to work on :) -- _ _ | |__ __ _| |_ ___ _ __ ___ __ _ _ __ | '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ | |_) | (_| | |_\__ \ | | | | | (_| | | | | |_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_| Running Debian GNU/Linux Sid (unstable) batsman dot geo at yahoo dot com eat Depends: cook | eat-out. But eat-out is non-free so that's out. And cook Recommends: clean-pans. -- Seen on #Debian