[#536] SEVG in bignum.c:505... — Sean Chittenden <sean@...>
$ ruby -e 'p [].to_s.strip.to_i'
5 messages
2002/10/13
[#537] darwin shared library patch — Eric Melville <eric@...>
In Darwin, the preferred way to build shared libraries is with two level
9 messages
2002/10/13
[#539] Re: darwin shared library patch
— "Akinori MUSHA" <knu@...>
2002/10/13
Hi,
[#544] Re: darwin shared library patch
— Eric Melville <eric@...>
2002/10/16
> The patch seems to make ENV[]= coredump.
[#546] Re: darwin shared library patch
— "Akinori MUSHA" <knu@...>
2002/10/16
At Thu, 17 Oct 2002 01:41:49 +0900,
[#541] Patch for MacOS X dln.c — Luc B駘anger <belanglu@...>
I have a patch for the dynamic linker in MacOS X, which permit to load
7 messages
2002/10/13
Wrtite barrier
From:
Torsten Rer <torsten.rueger@...>
Date:
2002-10-02 07:57:46 UTC
List:
ruby-core #516
Moi,
I hope I'm on the right list with this.
I'm trying to build an interface layer to a memory persistance library
(http://hibase.cs.hut.fi/technology.shtml)
The idea is to :
-- get objects from shades to ruby
-- use (read + write) in ruby, normal code, nothing extra
-- save only the modified ruby objects back
To implement this, I would need some kind of write barrier, so that I
could mark object "clean" when I load them, make them "dirty" during a
write and then only write the "dirty" ones back.
Does anyone have a good idea how to implement this ?
Cheers
Torsten