Aah, the << operator. I make a note in the code when I reviewed it
that there was something amiss. I have fixed it and checked it into
(the MEM2 branch). The copy_bug.rb and copy_bug2.rb are moved in to
rwtests and will run as part of 'rake memtests'. They clear now.
There was an issue in c
Trans,
The trunk had not been merged from MEM2 at all yet. It is still in
the 0.4pre state. If the MEM2 is deemed a better stable version then
I can merge back into the trunk.
We should make a project coding decision about where development
happens. I prefer development in branches, the tru
I did a little testing of << against my own application and found an
incompatibility.
<< now copies a node/tree before adding it to another. I had code
that added the node to a tree and then modified the node. This
modified the original and not the copy in the parented tree. I don't
see th
On 9/4/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
> I did a little testing of << against my own application and found an
> incompatibility.
>
> << now copies a node/tree before adding it to another. I had code
> that added the node to a tree and then modified the node. This
> modified the original
On Sep 4, 2007, at 17:09, TRANS wrote:
> On 9/4/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> I did a little testing of << against my own application and found an
>> incompatibility.
>>
>> << now copies a node/tree before adding it to another. I had code
>> that added the node to a tree and then
