Re: [libxml-devel] A couple suggested updates...

2006-05-28 Thread Ross Bamford
On Sun, 14 May 2006 06:56:47 +0100, Mark Van Holstyn <[EMAIL PROTECTED]> wrote: > I changed [], []=, and new to all accept symbols OR string, rather than > just strings. Does this seems like good functionality to anyone else? > Attatched is the patch should you find this functionality useful

Re: [libxml-devel] Thank you for reviving libxml

2006-05-28 Thread Ross Bamford
On Thu, 25 May 2006 19:30:30 +0100, Yann Klis <[EMAIL PROTECTED]> wrote: > Mark Van Holstyn a écrit : >> you do something like this... bar.find_first('Foo') to get the first >> child node of bar whose name is Foo. Also, to get all the children, >> you can do bar.find('*').each { |child| do somethi

Re: [libxml-devel] how to replace a node with another node?

2006-05-28 Thread Ross Bamford
On Thu, 25 May 2006 20:50:24 +0100, Doug Bryant <[EMAIL PROTECTED]> wrote: > Thanks Ross. That will work well for now. > > Are you responsible for reviving libxml-ruby? If so, thank you very > much! > Cool, I assume you got it working with the CVS head - I forgot to mention that, sorry..

[libxml-devel] exposing _private data

2006-05-28 Thread Ross Bamford
Feature request 4565 [1] concerns exposing the libxml2 _private member in libxml-ruby. This looks doable, but I wonder if anyone who knows more about libxml2 than I do has any thoughts? One potential problem I can think of is that libxslt apparently makes use of _private, so it might open u