News for hackers. Stuff that matters.

A comment on The Broken Promises of MRI/REE/YARV. Parent comment

Re:The Broken Promises of MRI/REE/YARV by jjore on Tuesday July 05, 2011 @07:47PM (#2732035)
Well, the problem here is that C using gems are going to often be memory corruptingly buggy until and unless either the gem source is updated to declare the proper parts volatile or Ruby's own C API is reworked to evolve this bug out of existence and then gems would have to be updated to use the API anyway.

Both problems are hard and the current state of affairs is apparently some random amount of the time we'll get memory corruption bugs.

[ Parent | on HN ]
Re:The Broken Promises of MRI/REE/YARV by KirinDave on Tuesday July 05, 2011 @07:54PM (#2732047)
It's worse than that. We don't actually know where it occurs. There are clearly some gems where it does, but it could also be occurring elsewhere in the VM.

Just figuring this out is a non-trivial project.

[ Parent | on HN ]