On 3 September 2010 16:16, Clifford Heath <[email protected]> wrote:
> While I cant vouch for it, I know that memory leaks was number one on Tim > Hunter's > priorities, and he claimed to have produced a release that was, barring > programmer > stupidity, basically free of leaks. In order to get around the issues with > the Ruby GC > not being able to see the image memory, he even provided a method to > release the > memory for an image. Now while manual release isn't exactly a 21st century > way of > going about things, it actually isn't a problem with significant objects > like images. > Nice. A manual free isn't ideal but it wouldn't bother me—I'd wrap it up with a block accessor that autofreed it anyway :) Glad to hear progress is being made. —Ben -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
