---- Reported by werner@yellowcouch.org 2007-11-07 15:48:10 ---- When cloning from a write to a read we need the ability to look up the value type in a central storage and return the object there instead of really creating a new one. This should ensure better memory management and makes caching of scheme functions possible. ---- Additional Comments From werner@yellowcouch.org 2007-11-09 14:03:07 ---- The proper way to do this is creating the readonly object and then translating it to the correct pointer. The translationstep is done using make_unique_object after its instantiation and readonly making step. --- Bug imported by werner@yellowcouch.org 2008-12-26 11:56 --- This bug was previously known as _bug_ 170 at http://werner.yellowcouch.org/borgflowbugs/0