From danj at 3skel.com  Wed Oct 10 12:31:28 2007
From: danj at 3skel.com (Dan Janowski)
Date: Wed, 10 Oct 2007 12:31:28 -0400
Subject: [libxml-devel] Release 0.5.2
Message-ID: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>

Release 0.5.2 MEM2 release fixes all known and reported memory faults.

project page

http://rubyforge.org/projects/libxml/

Try it out if you can.

Dan

From danj.3skel at gmail.com  Wed Oct 10 12:29:11 2007
From: danj.3skel at gmail.com (dan)
Date: Wed, 10 Oct 2007 09:29:11 -0700
Subject: [libxml-devel] release 0.5.2
Message-ID: <1192033751.311536.260940@g4g2000hsf.googlegroups.com>

Release 0.5.2 MEM2 release fixes all known and reported memory faults.

project page

http://rubyforge.org/projects/libxml/

Try it out if you can.

Dan


From cjbottaro at alumni.cs.utexas.edu  Wed Oct 10 19:42:46 2007
From: cjbottaro at alumni.cs.utexas.edu (Christopher J. Bottaro)
Date: Wed, 10 Oct 2007 18:42:46 -0500
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
Message-ID: <c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>

Did the API change?  XML::Document#find used to return XML::Node::Set
and now it returns XML::XPath::Object.  Where can I read about the API
changes?

Thanks.

On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
> Release 0.5.2 MEM2 release fixes all known and reported memory faults.
>
> project page
>
> http://rubyforge.org/projects/libxml/
>
> Try it out if you can.
>
> Dan
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
>

From danj at 3skel.com  Thu Oct 11 00:06:49 2007
From: danj at 3skel.com (Dan Janowski)
Date: Thu, 11 Oct 2007 00:06:49 -0400
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
	<c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>
Message-ID: <FC0F957C-5754-4101-8841-D9F63CBCB4E7@3skel.com>

XML::XPath::Object behaves the same as XML::Node::Set and implements  
all Set methods. There is a .set receiver on XPath::Object that  
returns a XML::Node::Set, but it is really a pseudo object as it  
passes all methods through to Object.

There are no updates to the documentation at this time. These changes  
just occurred. Anyone wishing to do embedded rdoc, please contact me.

Dan

On Oct 10, 2007, at 19:42, Christopher J. Bottaro wrote:

> Did the API change?  XML::Document#find used to return XML::Node::Set
> and now it returns XML::XPath::Object.  Where can I read about the API
> changes?
>
> Thanks.
>
> On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
>> Release 0.5.2 MEM2 release fixes all known and reported memory  
>> faults.
>>
>> project page
>>
>> http://rubyforge.org/projects/libxml/
>>
>> Try it out if you can.
>>
>> Dan
>> _______________________________________________
>> libxml-devel mailing list
>> libxml-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/libxml-devel
>>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel


From cjbottaro at alumni.cs.utexas.edu  Thu Oct 11 01:45:36 2007
From: cjbottaro at alumni.cs.utexas.edu (Christopher J. Bottaro)
Date: Thu, 11 Oct 2007 00:45:36 -0500
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <FC0F957C-5754-4101-8841-D9F63CBCB4E7@3skel.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
	<c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>
	<FC0F957C-5754-4101-8841-D9F63CBCB4E7@3skel.com>
Message-ID: <c19e6adb0710102245t3b7c369bxc7a2e8e93f6ec5e5@mail.gmail.com>

Hey Dan,
[] is not implemented for XML::XPath::Object, but it is for
XML::Node::Set.  I made an abstraction layer with pluggable backend
(libxml, rexml) so it wasn't a big deal for me to implement [] by
using XML::XPath::Object#collect to convert it to an array, but I just
thought you'd like to know.

Thanks for the reply.
-- Christopher

On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
> XML::XPath::Object behaves the same as XML::Node::Set and implements
> all Set methods. There is a .set receiver on XPath::Object that
> returns a XML::Node::Set, but it is really a pseudo object as it
> passes all methods through to Object.
>
> There are no updates to the documentation at this time. These changes
> just occurred. Anyone wishing to do embedded rdoc, please contact me.
>
> Dan
>
> On Oct 10, 2007, at 19:42, Christopher J. Bottaro wrote:
>
> > Did the API change?  XML::Document#find used to return XML::Node::Set
> > and now it returns XML::XPath::Object.  Where can I read about the API
> > changes?
> >
> > Thanks.
> >
> > On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
> >> Release 0.5.2 MEM2 release fixes all known and reported memory
> >> faults.
> >>
> >> project page
> >>
> >> http://rubyforge.org/projects/libxml/
> >>
> >> Try it out if you can.
> >>
> >> Dan
> >> _______________________________________________
> >> libxml-devel mailing list
> >> libxml-devel at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/libxml-devel
> >>
> > _______________________________________________
> > libxml-devel mailing list
> > libxml-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/libxml-devel
>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
>

From danj at 3skel.com  Thu Oct 11 07:42:26 2007
From: danj at 3skel.com (Dan Janowski)
Date: Thu, 11 Oct 2007 07:42:26 -0400
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <c19e6adb0710102245t3b7c369bxc7a2e8e93f6ec5e5@mail.gmail.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
	<c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>
	<FC0F957C-5754-4101-8841-D9F63CBCB4E7@3skel.com>
	<c19e6adb0710102245t3b7c369bxc7a2e8e93f6ec5e5@mail.gmail.com>
Message-ID: <5FA26E2A-B7C2-46A2-A305-848E06D349ED@3skel.com>

That is unintentional, it should implement [].
Dan

On Oct 11, 2007, at 01:45, Christopher J. Bottaro wrote:

> Hey Dan,
> [] is not implemented for XML::XPath::Object, but it is for
> XML::Node::Set.  I made an abstraction layer with pluggable backend
> (libxml, rexml) so it wasn't a big deal for me to implement [] by
> using XML::XPath::Object#collect to convert it to an array, but I just
> thought you'd like to know.
>
> Thanks for the reply.
> -- Christopher
>
> On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
>> XML::XPath::Object behaves the same as XML::Node::Set and implements
>> all Set methods. There is a .set receiver on XPath::Object that
>> returns a XML::Node::Set, but it is really a pseudo object as it
>> passes all methods through to Object.
>>
>> There are no updates to the documentation at this time. These changes
>> just occurred. Anyone wishing to do embedded rdoc, please contact me.
>>
>> Dan
>>
>> On Oct 10, 2007, at 19:42, Christopher J. Bottaro wrote:
>>
>>> Did the API change?  XML::Document#find used to return  
>>> XML::Node::Set
>>> and now it returns XML::XPath::Object.  Where can I read about  
>>> the API
>>> changes?
>>>
>>> Thanks.
>>>
>>> On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
>>>> Release 0.5.2 MEM2 release fixes all known and reported memory
>>>> faults.
>>>>
>>>> project page
>>>>
>>>> http://rubyforge.org/projects/libxml/
>>>>
>>>> Try it out if you can.
>>>>
>>>> Dan
>>>> _______________________________________________
>>>> libxml-devel mailing list
>>>> libxml-devel at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/libxml-devel
>>>>
>>> _______________________________________________
>>> libxml-devel mailing list
>>> libxml-devel at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/libxml-devel
>>
>> _______________________________________________
>> libxml-devel mailing list
>> libxml-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/libxml-devel
>>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel


From cjbottaro at alumni.cs.utexas.edu  Thu Oct 11 14:46:13 2007
From: cjbottaro at alumni.cs.utexas.edu (Christopher J. Bottaro)
Date: Thu, 11 Oct 2007 13:46:13 -0500
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <5FA26E2A-B7C2-46A2-A305-848E06D349ED@3skel.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
	<c19e6adb0710101642i45bff90bh3acc15a19165eb2f@mail.gmail.com>
	<FC0F957C-5754-4101-8841-D9F63CBCB4E7@3skel.com>
	<c19e6adb0710102245t3b7c369bxc7a2e8e93f6ec5e5@mail.gmail.com>
	<5FA26E2A-B7C2-46A2-A305-848E06D349ED@3skel.com>
Message-ID: <c19e6adb0710111146p2909c72ev4adef26f08ddeb24@mail.gmail.com>

Great work, Dan.  After a little work I was seeing this:
227 tests, 1197 assertions, 0 failures, 0 errors

:)  Big change from the segfaults we were getting before.

A few things I noticed...
*  as I mentioned before, [] is not implemented for XML::XPath::Object
(which is the return value of XML::Document#find and XML::Node#find)
*  XML::Node#[]=(val) expects val to be a string or nil.  before it
would accept integers.
*  no more implicit copies if appending a node from document a into document b.
*  I actually did get a segfault one time while running a unit test
that had a failure, but then I fixed a test and it went away.

All in all, great work!  We're now using libxml instead of rexml (at
least until another segfault rears it's ugly head)!

Thanks,
-- Christopher

P.S.  Our test suite runs 3 times faster with libxml vs. rexml.  :)

On 10/11/07, Dan Janowski <danj at 3skel.com> wrote:
> That is unintentional, it should implement [].
> Dan
>
> On Oct 11, 2007, at 01:45, Christopher J. Bottaro wrote:
>
> > Hey Dan,
> > [] is not implemented for XML::XPath::Object, but it is for
> > XML::Node::Set.  I made an abstraction layer with pluggable backend
> > (libxml, rexml) so it wasn't a big deal for me to implement [] by
> > using XML::XPath::Object#collect to convert it to an array, but I just
> > thought you'd like to know.
> >
> > Thanks for the reply.
> > -- Christopher
> >
> > On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
> >> XML::XPath::Object behaves the same as XML::Node::Set and implements
> >> all Set methods. There is a .set receiver on XPath::Object that
> >> returns a XML::Node::Set, but it is really a pseudo object as it
> >> passes all methods through to Object.
> >>
> >> There are no updates to the documentation at this time. These changes
> >> just occurred. Anyone wishing to do embedded rdoc, please contact me.
> >>
> >> Dan
> >>
> >> On Oct 10, 2007, at 19:42, Christopher J. Bottaro wrote:
> >>
> >>> Did the API change?  XML::Document#find used to return
> >>> XML::Node::Set
> >>> and now it returns XML::XPath::Object.  Where can I read about
> >>> the API
> >>> changes?
> >>>
> >>> Thanks.
> >>>
> >>> On 10/10/07, Dan Janowski <danj at 3skel.com> wrote:
> >>>> Release 0.5.2 MEM2 release fixes all known and reported memory
> >>>> faults.
> >>>>
> >>>> project page
> >>>>
> >>>> http://rubyforge.org/projects/libxml/
> >>>>
> >>>> Try it out if you can.
> >>>>
> >>>> Dan
> >>>> _______________________________________________
> >>>> libxml-devel mailing list
> >>>> libxml-devel at rubyforge.org
> >>>> http://rubyforge.org/mailman/listinfo/libxml-devel
> >>>>
> >>> _______________________________________________
> >>> libxml-devel mailing list
> >>> libxml-devel at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/libxml-devel
> >>
> >> _______________________________________________
> >> libxml-devel mailing list
> >> libxml-devel at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/libxml-devel
> >>
> > _______________________________________________
> > libxml-devel mailing list
> > libxml-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/libxml-devel
>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel
>

From stephen.bannasch at deanbrook.org  Fri Oct 12 04:30:52 2007
From: stephen.bannasch at deanbrook.org (Stephen Bannasch)
Date: Fri, 12 Oct 2007 04:30:52 -0400
Subject: [libxml-devel] lots of 'No definition for ..." when gem install
	0.5.2.0
Message-ID: <p06240802c334e0a7cac5@[68.244.241.45]>

I got lots of "No definition for ..." messages when doing a gem 
install of the most recent libxml-ruby -- is this OK?

System: macosx 10.4.10

$ sudo gem update 'libxml-ruby'
Updating installed gems...
Need to update 28 gems from http://gems.rubyforge.org
............................
complete
Attempting remote update of libxml-ruby
Building native extensions.  This could take a while...
Successfully installed libxml-ruby-0.5.2.0
Installing ri documentation for libxml-ruby-0.5.2.0...

No definition for ruby_xml_html_parser_new_file

No definition for ruby_xml_html_parser_new_io

No definition for ruby_xml_html_parser_filename_get

No definition for ruby_xml_html_parser_filename_set

No definition for ruby_xml_html_parser_io_get

No definition for ruby_xml_html_parser_io_set

No definition for input_callbacks_register_input_callbacks

No definition for input_callbacks_add_scheme

No definition for input_callbacks_remove_scheme

No definition for ruby_xml_node2_new_native

Enclosing class/module 'cXMLSaxParser' for module Callbacks not known

No definition for ruby_xml_state_used_p

No definition for ruby_xml_state_use

No definition for ruby_xml_xpath_findva

No definition for ruby_xml_xpath_object_set_type

No definition for ruby_xml_xpath_object_string
Installing RDoc documentation for libxml-ruby-0.5.2.0...

No definition for ruby_xml_html_parser_new_file

No definition for ruby_xml_html_parser_new_io

No definition for ruby_xml_html_parser_filename_get

No definition for ruby_xml_html_parser_filename_set

No definition for ruby_xml_html_parser_io_get

No definition for ruby_xml_html_parser_io_set

No definition for input_callbacks_register_input_callbacks

No definition for input_callbacks_add_scheme

No definition for input_callbacks_remove_scheme

No definition for ruby_xml_node2_new_native

Enclosing class/module 'cXMLSaxParser' for module Callbacks not known

No definition for ruby_xml_state_used_p

No definition for ruby_xml_state_use

No definition for ruby_xml_xpath_findva

No definition for ruby_xml_xpath_object_set_type

No definition for ruby_xml_xpath_object_string
Gems: [libxml-ruby] updated

From danj at 3skel.com  Fri Oct 12 22:10:27 2007
From: danj at 3skel.com (Dan Janowski)
Date: Fri, 12 Oct 2007 22:10:27 -0400
Subject: [libxml-devel] lots of 'No definition for ..." when gem install
	0.5.2.0
In-Reply-To: <p06240802c334e0a7cac5@[68.244.241.45]>
References: <p06240802c334e0a7cac5@[68.244.241.45]>
Message-ID: <7F7F59F0-A4E1-4DBF-88F5-4C18A23F2D99@3skel.com>

These appear to be only related to the ri documentation (that's  
missing).

Dan

On Oct 12, 2007, at 04:30, Stephen Bannasch wrote:

> I got lots of "No definition for ..." messages when doing a gem
> install of the most recent libxml-ruby -- is this OK?
>
> System: macosx 10.4.10
>
> $ sudo gem update 'libxml-ruby'
> Updating installed gems...
> Need to update 28 gems from http://gems.rubyforge.org
> ............................
> complete
> Attempting remote update of libxml-ruby
> Building native extensions.  This could take a while...
> Successfully installed libxml-ruby-0.5.2.0
> Installing ri documentation for libxml-ruby-0.5.2.0...
>
> No definition for ruby_xml_html_parser_new_file
>
> No definition for ruby_xml_html_parser_new_io
>
> No definition for ruby_xml_html_parser_filename_get
>
> No definition for ruby_xml_html_parser_filename_set
>
> No definition for ruby_xml_html_parser_io_get
>
> No definition for ruby_xml_html_parser_io_set
>
> No definition for input_callbacks_register_input_callbacks
>
> No definition for input_callbacks_add_scheme
>
> No definition for input_callbacks_remove_scheme
>
> No definition for ruby_xml_node2_new_native
>
> Enclosing class/module 'cXMLSaxParser' for module Callbacks not known
>
> No definition for ruby_xml_state_used_p
>
> No definition for ruby_xml_state_use
>
> No definition for ruby_xml_xpath_findva
>
> No definition for ruby_xml_xpath_object_set_type
>
> No definition for ruby_xml_xpath_object_string
> Installing RDoc documentation for libxml-ruby-0.5.2.0...
>
> No definition for ruby_xml_html_parser_new_file
>
> No definition for ruby_xml_html_parser_new_io
>
> No definition for ruby_xml_html_parser_filename_get
>
> No definition for ruby_xml_html_parser_filename_set
>
> No definition for ruby_xml_html_parser_io_get
>
> No definition for ruby_xml_html_parser_io_set
>
> No definition for input_callbacks_register_input_callbacks
>
> No definition for input_callbacks_add_scheme
>
> No definition for input_callbacks_remove_scheme
>
> No definition for ruby_xml_node2_new_native
>
> Enclosing class/module 'cXMLSaxParser' for module Callbacks not known
>
> No definition for ruby_xml_state_used_p
>
> No definition for ruby_xml_state_use
>
> No definition for ruby_xml_xpath_findva
>
> No definition for ruby_xml_xpath_object_set_type
>
> No definition for ruby_xml_xpath_object_string
> Gems: [libxml-ruby] updated
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel


From marc at bloodnok.com  Thu Oct 18 16:43:59 2007
From: marc at bloodnok.com (Marc Munro)
Date: Thu, 18 Oct 2007 13:43:59 -0700
Subject: [libxml-devel] Release 0.5.2
In-Reply-To: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
References: <5C3DCBAD-809D-4A9A-8E91-C01ECC868256@3skel.com>
Message-ID: <1192740239.29008.28.camel@bloodnok.com>

Dan,
Took me a while to try it out.  It still segfaults, while the gem
version (0.3.9.1, I think) does not.  Here is the backtrace:


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ce78c0 (LWP 19967)]
0xb7cb21a7 in ruby_xml_xpath_object_mark (xpop=0x8fff4b0)
    at ruby_xml_xpath_object.c:22
22          for (i=0; i<xpop->nodesetval->nodeNr; i++) {
(gdb) bt
#0  0xb7cb21a7 in ruby_xml_xpath_object_mark (xpop=0x8fff4b0)
    at ruby_xml_xpath_object.c:22
#1  0xb7ee3940 in ?? () from /usr/lib/libruby1.8.so.1.8
#2  0x08fff4b0 in ?? ()
#3  0x080caf38 in ?? ()
#4  0xbfc683a8 in ?? ()
#5  0xb7ee3d4e in ?? () from /usr/lib/libruby1.8.so.1.8
#6  0xb7ee4b29 in rb_newobj () from /usr/lib/libruby1.8.so.1.8
#7  0xb7ee3f29 in ?? () from /usr/lib/libruby1.8.so.1.8
#8  0xb7ee33a4 in ruby_stack_check () from /usr/lib/libruby1.8.so.1.8
#9  0xb7ee4131 in ?? () from /usr/lib/libruby1.8.so.1.8
#10 0xbfc683e8 in ?? ()
#11 0xbfc9f7e4 in ?? ()
#12 0x080c99b8 in ?? ()
#13 0x00003a67 in ?? ()
#14 0x00000000 in ?? ()

If you need it, I can probably package up my code for you though I
suspect it will not break in the same way on a different machine.  I am
also happy to try to perform more debugging for you remotely.

Let me know what I can do.

__
Marc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://rubyforge.org/pipermail/libxml-devel/attachments/20071018/75d68b37/attachment.bin 

From jprince at icmb.utexas.edu  Thu Oct 18 17:21:02 2007
From: jprince at icmb.utexas.edu (John Prince)
Date: Thu, 18 Oct 2007 16:21:02 -0500
Subject: [libxml-devel] XMLParser and libxml incompatibility
Message-ID: <364f41440710181421s67098509i49c912b6568169cd@mail.gmail.com>

I was writing some code where I parse some files with libxml and some with
XMLParser.  After some effort, I finally realized that there is in
incompatibility with the two libraries:

require 'xmlparser'
xml_string = "<x><y></y></x>"
XMLParser.new.parse(xml_string)

-------# -> No errors

require 'xmlparser'
require 'xml/libxml'
xml_string = "<x><y></y></x>"
XMLParser.new.parse(xml_string)


-------# -> test_sanity.rb:6:in `parse': wrong number of arguments (1 for 0)
(ArgumentError)
        from test_sanity.rb:6

Perhaps the XML::Parser#parse method is clobbering XMLParser's method?

If you try to work around this by redefining the parse method in XMLParser:
require 'xmlparser'

class XMLParser
  alias_method :diff_name, :parse
end

require 'xml/libxml'

xml_string = "<x><y></y></x>"
XMLParser.new.diff_name(xml_string)

-------# -> test_sanity.rb:10: [BUG] Segmentation fault
ruby 1.8.5 (2006-08-25) [i486-linux]

Aborted (core dumped)

Since these are both very useful xml parsing libraries, it would be nice if
both could be used in the same program...

Does anyone know of any work around in the meantime?

John Prince
UT Austin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/libxml-devel/attachments/20071018/8c3b33cb/attachment.html 

From danj at 3skel.com  Fri Oct 19 20:26:54 2007
From: danj at 3skel.com (Dan Janowski)
Date: Fri, 19 Oct 2007 20:26:54 -0400
Subject: [libxml-devel] XMLParser and libxml incompatibility
In-Reply-To: <364f41440710181421s67098509i49c912b6568169cd@mail.gmail.com>
References: <364f41440710181421s67098509i49c912b6568169cd@mail.gmail.com>
Message-ID: <282E9FE2-0AED-4AE2-9C2C-F0963AAB70EC@3skel.com>

libxml is entirely defined within the XML module. First, I hope you  
asked this same question to the developers of xmlparser. Second, if  
you want help you are going to have to get your hands a bit dirtier  
and provide some useful information about the state of module  
definitions as well as a gdb stack trace from the segv.

Dan

On Oct 18, 2007, at 17:21, John Prince wrote:

> I was writing some code where I parse some files with libxml and  
> some with XMLParser.  After some effort, I finally realized that  
> there is in incompatibility with the two libraries:
>
> require 'xmlparser'
> xml_string = "<x><y></y></x>"
> XMLParser.new.parse(xml_string)
>
> -------# -> No errors
>
> require 'xmlparser'
> require 'xml/libxml'
> xml_string = "<x><y></y></x>"
> XMLParser.new.parse(xml_string)
>
>
> -------# -> test_sanity.rb:6:in `parse': wrong number of arguments  
> (1 for 0) (ArgumentError)
>         from test_sanity.rb:6
>
> Perhaps the XML::Parser#parse method is clobbering XMLParser's method?
>
> If you try to work around this by redefining the parse method in  
> XMLParser:
> require 'xmlparser'
>
> class XMLParser
>   alias_method :diff_name, :parse
> end
>
> require 'xml/libxml'
>
> xml_string = "<x><y></y></x>"
> XMLParser.new.diff_name(xml_string)
>
> -------# -> test_sanity.rb:10: [BUG] Segmentation fault
> ruby 1.8.5 (2006-08-25) [i486-linux]
>
> Aborted (core dumped)
>
> Since these are both very useful xml parsing libraries, it would be  
> nice if both could be used in the same program...
>
> Does anyone know of any work around in the meantime?
>
> John Prince
> UT Austin
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel


From fabrice.talbot at gmail.com  Wed Oct 24 16:28:25 2007
From: fabrice.talbot at gmail.com (Fabrice (GMail))
Date: Wed, 24 Oct 2007 13:28:25 -0700
Subject: [libxml-devel] Problem installing libxml-ruby-0.5.2 on windows
Message-ID: <20071024205623.68E8318585DC@rubyforge.org>

Hi,

 

I checked the mailing list archives and did not find any answers to this
issue.

 

I get the following error when running "gem install -r libxml-ruby".

 

*****************************************************************
checking for socket() in socket.lib... no
checking for gethostbyname() in nsl.lib... no
checking for atan() in m.lib... yes
checking for inflate() in z.lib... no
checking for inflate() in zlib.lib... no
checking for inflate() in zlib1.lib... no
.

*****************************************************************

 

As suggested on libxml.rubyforge.org, I ran "ruby extconf.rb" and specified
the following options: -with-xml2-dir, --with-iconv-dir, --with-zlib-dir. I
got the same error message (FYI: I downloaded pre-compiled libraries for
Windows).

 

This is driving me crazy since I do need a XML/XSLT parser urgently for my
Ruby application.

 

I would greatly appreciate if someone could take the time to give me a few
hints on how to solve this issue.

 

Thanks,

Fabrice

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/libxml-devel/attachments/20071024/62b3f07c/attachment-0001.html 

From danj at 3skel.com  Wed Oct 24 19:49:25 2007
From: danj at 3skel.com (Dan Janowski)
Date: Wed, 24 Oct 2007 19:49:25 -0400
Subject: [libxml-devel] Problem installing libxml-ruby-0.5.2 on windows
In-Reply-To: <20071024205623.68E8318585DC@rubyforge.org>
References: <20071024205623.68E8318585DC@rubyforge.org>
Message-ID: <FB7C4E2B-C01D-404C-BE0C-49B7543C19D7@3skel.com>

The real info needed is in mkmf.log. Check to see if the option for  
libz is doing what you think it should.
Dan

On Oct 24, 2007, at 16:28, Fabrice ((GMail)) wrote:

> Hi,
>
>
>
> I checked the mailing list archives and did not find any answers to  
> this issue.
>
>
>
> I get the following error when running ?gem install -r libxml-ruby?.
>
>
>
> *****************************************************************
> checking for socket() in socket.lib... no
> checking for gethostbyname() in nsl.lib... no
> checking for atan() in m.lib... yes
> checking for inflate() in z.lib... no
> checking for inflate() in zlib.lib... no
> checking for inflate() in zlib1.lib... no
> ?
>
> *****************************************************************
>
>
>
> As suggested on libxml.rubyforge.org, I ran ?ruby extconf.rb? and  
> specified the following options: ?with-xml2-dir, --with-iconv-dir,  
> --with-zlib-dir. I got the same error message (FYI: I downloaded  
> pre-compiled libraries for Windows).
>
>
>
> This is driving me crazy since I do need a XML/XSLT parser urgently  
> for my Ruby application.
>
>
>
> I would greatly appreciate if someone could take the time to give  
> me a few hints on how to solve this issue.
>
>
>
> Thanks,
>
> Fabrice
>
>
>
>
>
>
>
> _______________________________________________
> libxml-devel mailing list
> libxml-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/libxml-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/libxml-devel/attachments/20071024/52313493/attachment.html 

From fabrice.talbot at gmail.com  Thu Oct 25 13:37:19 2007
From: fabrice.talbot at gmail.com (Fabrice (GMail))
Date: Thu, 25 Oct 2007 10:37:19 -0700
Subject: [libxml-devel] Problem installing libxml-ruby-0.5.2 on windows
In-Reply-To: <FB7C4E2B-C01D-404C-BE0C-49B7543C19D7@3skel.com>
Message-ID: <20071025173716.5EB781858656@rubyforge.org>

I had already checked that and my options are passed correctly (as far as I
can see). 

 

See below an extract of the 'mkmf' log file for zlib

 

Fabrice

 

have_library: checking for inflate() in z.lib... -------------------- no

 

"cl -nologo -Feconftest -I.
-ID:/MyDev/InstantRails/ruby/lib/ruby/1.8/i386-mswin32 -I.
-ID:/MyDev/InstantRails/ruby/lib/ruby/1.8/i386-mswin32 -ID:/lib/zlib/include
-ID:/lib/libxml2/include -ID:/lib/iconv/include  -MD -Zi -O2b2xg- -G6
conftest.c   msvcrt-ruby18-static.lib z.lib  oldnames.lib user32.lib
advapi32.lib ws2_32.lib   -link    -libpath:"D:/MyDev/InstantRails/ruby/lib"
-libpath:"D:/lib/zlib/lib" -libpath:"D:/lib/libxml2/lib"
-libpath:"D:/lib/iconv/lib" -libpath:"D:/MyDev/InstantRails/ruby/lib"
-stack:0x2000000"

checked program was:

/* begin */

1: #define WIN32_LEAN_AND_MEAN

2: #include <winsock2.h>

3: #include <windows.h>

4: 

5: /*top*/

6: int main() { return 0; }

7: int t() { void ((*volatile p)()); p = (void ((*)()))inflate; return 0; }

/* end */

 

"cl -nologo -Feconftest -I.
-ID:/MyDev/InstantRails/ruby/lib/ruby/1.8/i386-mswin32 -I.
-ID:/MyDev/InstantRails/ruby/lib/ruby/1.8/i386-mswin32 -ID:/lib/zlib/include
-ID:/lib/libxml2/include -ID:/lib/iconv/include  -MD -Zi -O2b2xg- -G6
conftest.c   msvcrt-ruby18-static.lib z.lib  oldnames.lib user32.lib
advapi32.lib ws2_32.lib   -link    -libpath:"D:/MyDev/InstantRails/ruby/lib"
-libpath:"D:/lib/zlib/lib" -libpath:"D:/lib/libxml2/lib"
-libpath:"D:/lib/iconv/lib" -libpath:"D:/MyDev/InstantRails/ruby/lib"
-stack:0x2000000"

checked program was:

/* begin */

1: /*top*/

2: int main() { return 0; }

3: int t() { inflate(); return 0; }

/* end */

 

--------------------

 

  _____  

From: libxml-devel-bounces at rubyforge.org
[mailto:libxml-devel-bounces at rubyforge.org] On Behalf Of Dan Janowski
Sent: Wednesday, October 24, 2007 4:49 PM
To: libxml-devel at rubyforge.org
Subject: Re: [libxml-devel] Problem installing libxml-ruby-0.5.2 on windows

 

The real info needed is in mkmf.log. Check to see if the option for libz is
doing what you think it should.

Dan

 

On Oct 24, 2007, at 16:28, Fabrice ((GMail)) wrote:





Hi,

 

I checked the mailing list archives and did not find any answers to this
issue.

 

I get the following error when running "gem install -r libxml-ruby".

 

*****************************************************************
checking for socket() in socket.lib... no
checking for gethostbyname() in nsl.lib... no
checking for atan() in m.lib... yes
checking for inflate() in z.lib... no
checking for inflate() in zlib.lib... no
checking for inflate() in zlib1.lib... no
.

*****************************************************************

 

As suggested on libxml.rubyforge.org, I ran "ruby extconf.rb" and specified
the following options: -with-xml2-dir, --with-iconv-dir, --with-zlib-dir. I
got the same error message (FYI: I downloaded pre-compiled libraries for
Windows).

 

This is driving me crazy since I do need a XML/XSLT parser urgently for my
Ruby application.

 

I would greatly appreciate if someone could take the time to give me a few
hints on how to solve this issue.

 

Thanks,

Fabrice

 

 

 

_______________________________________________

libxml-devel mailing list

libxml-devel at rubyforge.org

http://rubyforge.org/mailman/listinfo/libxml-devel

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/libxml-devel/attachments/20071025/a76dc35b/attachment-0001.html 

From mortee.lists at kavemalna.hu  Fri Oct 26 12:26:11 2007
From: mortee.lists at kavemalna.hu (mortee)
Date: Fri, 26 Oct 2007 18:26:11 +0200
Subject: [libxml-devel] xpath searching without specifying namespace?
Message-ID: <fft4bd$bi1$1@ger.gmane.org>


Hi,

I just wanted to give libxml a go, because it seemed quite a bit faster
than my current solution.

The docs for XML::XPath.find suggest that if I omit the namespace
specification, then "matching nodes from any namespace will be included".

My problem is that when I fed it an XML file with a DOCTYPE declaration
and a namespace spec on the root node, no matter what element name I was
trying to search for, it returned an empty result set.

I could work around the problem by removing *both* the DOCTYPE and the
NS attribute from the root node; in this case simple unqualified element
names were found.

I could also have it to find what I'm looking for by specifying a
"prefix:ns_uri" as the second parameter to #find, and have any element
names in my xpath be qualified by the specified prefix. This however is
an overkill for me, as the whole document has one single namespace, so I
really don't want any NS-based filtering on my xpath query.

So the question is, why doesn't it find unqualified element names when I
omit the second parameter from #find, and how could I achieve it?

thx
mortee