From: Austin Ziegler Date: 2007-12-13T22:18:01+09:00 Subject: Re: [Spam] Re: What's the status of compiler/compiling on windows? On 12/13/07, Joe Swatosh wrote: > On Dec 12, 2007 1:55 PM, Austin Ziegler wrote: > > And the *reason* it's not a theoretical scenario is that Unix doesn't > > have this problem (multiple runtimes) in > 99% of cases. Most Unixes > > only have one runtime installed and cannot actually have another > > runtime installed. Therefore, there's not multiple heaps involved. > > Therefore, it's a common case to have an API that says "this C call > > allocates memory; remember to free it when you're done with it." There > > should be an library_api_free call for every library (e.g., zlib_free, > > openssl_free, etc.) just in case, but it's Not An Issue on Unix. > > If everyone used ruby_xmalloc and ruby_xfree, would this part of the binary > extension problem be addressed? No, unfortunately. It would help when you're embedding Ruby in something else, but most people do something like that anyway to permit garbage collection, at least in their extension layer. IIRC. ;) The problem is in the libraries that may be wrapped, such as ncurses or zlib. -austin -- Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/ * austin@halostatue.ca * http://www.halostatue.ca/feed/ * austin@zieglers.ca