This bug report is interesting:
http://rubyforge.org/tracker/index.php?func=detail&aid=19772&group_id=494&atid=1971
Basically, the code compares two nodes using the == operator, assuming
that == means equal? (same object) and not eql? (equivalent object).
Right now libxml-ruby does the opposi
Bugs item #19738, was opened at 2008-04-23 18:01
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19738&group_id=494
Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Nobody (None)
>Assigned to: Charlie Savage (cfis)
Sum
Bugs item #19772, was opened at 2008-04-25 08:40
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19772&group_id=494
Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 3
Submitted By: Nobody (None)
>Assigned to: Charlie Savage (cfis)
Sum
Bugs item #14618, was opened at 2007-10-10 17:55
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1971&aid=14618&group_id=494
Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Dave Howell (snarke)
>Assigned to: Charlie Savage (cf
If you can go back a tag the prior release, that would be good, but
since you already committed there no reason to make a big fuss about
it (as long as everything is still working! ;) We can just move
forward from here.
Tagged.
Does anyone mind if I clean out the old branches in the repository?
Sean Chittenden wrote:
If you can go back a tag the prior release, that would be good, but
since you already committed there no reason to make a big fuss about
it (as long as everything is still working! ;) We can just move
forward from here.
Tagged.
Does anyone mind if I clean out the old b
Is there any reason to nuke 'em? -sc
I was thinking more along the lines of whether there is any reason
to keep them.
My thinking in getting rid of them is the repository will have less
clutter (less code) and check out times will be significantly
reduced. Since they are now dead code,
I think this is a vestige of the old fact that there could be two ruby
objects that referred to the same XML node. Since I removed that and
now there is only a one-to-one relationship between the ruby peer and
the XML node, if == is equivalent to equal? and equal? is object
identity, then i
Dan Janowski wrote:
I think this is a vestige of the old fact that there could be two ruby
objects that referred to the same XML node. Since I removed that and now
there is only a one-to-one relationship between the ruby peer and the
XML node, if == is equivalent to equal? and equal? is objec
