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@rubyforge.org
http://rubyforge.org/mailman/listinfo
real problem occurs.
I am open to suggestions, but I can't do this part on my own.
Dan
On Wed, 5 Mar 2008 12:43:01 -0800
Sean Chittenden <[EMAIL PROTECTED]> wrote:
> > Seeing that no one else has responded
>
> I don't know if it's been nixed or not, but the
The IO component of the extension has not been
carefully examined in the new mem model. It is
quite possible that the mark is not propogating
to the io instances. This I can look at (it seems
concrete).
Dan
On Mon, 10 Mar 2008 09:47:02 -0700
Sean Chittenden <[EMAIL PROTECTED]>
Hi,
I have just started using libxml2 for ruby and have come to a
problem. Attribute traversal is broken. Only the first attr is
accessible from .properties.
Here is an illustration:
require 'rubygems'
require 'libxml'
p=XML::Parser.string(%q{type="xs:positiveInteger"/>})
d=p.parse
irb(ma
updated patch include prototype.
libxml-ruby-0.3.8.1.patch
Description: Binary data
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
as performance. Is the
libXML memory model unstable to keep pointer references to?
Dan
On Jun 9, 2006, at 13:54, Ross Bamford wrote:
> On Fri, 09 Jun 2006 17:36:16 +0100, Dan Janowski <[EMAIL PROTECTED]>
> wrote:
>
>> Hi,
>>
>> I have just started using li
Another attribute bug. calling .properties when node does not include
attributes returns a new cXMLAttr when it should return nil. Any
calls on the cXMLAttr results in a SEGV since there is no underlying
attr structure.
This includes prior attr patch.
Dan
libxml-ruby-0.3.8.2.patch
good idea. It seems to be bigger than one
person can manage on a part time basis, but there needs to be a
unified vision of how to approach the problem.
Dan
On Jul 12, 2007, at 13:03, TRANS wrote:
> I see that Ross Bramford is not even listed as a project member any
> more --let alo
It is summer, is Sean just on vacation?
Dan
On Aug 5, 2007, at 09:08, TRANS wrote:
> Hi All,
>
> I'm considering forking the libxml project. Once again I can't get a
> hold of Sean Chittenden. So we can't get any new developers on the
> project with commit rights
strategy for dealing with
them?
Dan
On Aug 6, 2007, at 16:29, TRANS wrote:
> On 8/6/07, Ross Bamford <[EMAIL PROTECTED]> wrote:
>
>> I'd say there's too much good code in there to just throw it away
>> - a lot
>> of the current code works well, an
This is good foreign intelligence. In your searching, did you find
anything to indicate that the py interface had been changed to cope
with these issues from 2004?
Dan
On Aug 23, 2007, at 14:32, Charlie Savage wrote:
> Seems the python community has some of the same issues.
>
If they are to be separate units, I vote for separate modules. A
common virtual release tag can be applied to both to deal with the
synchronization issue.
Dan
On Aug 24, 2007, at 18:39, TRANS wrote:
> On 8/23/07, Charlie Savage <[EMAIL PROTECTED]> wrote:
>>> In the secon
.
Dan
On Aug 23, 2007, at 14:25, Sean Chittenden wrote:
> Having spent a great deal of time with this, I'm now of the following
> opinion of this library: when initially writing this module, I
> exposed too much of libxml to Ruby and the memory models and object/
> tree
particularly looking for ones that just use the node
operations.
Looking forward to your dastardly tests.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
Tom,
This is now memory stable. The script completes using only 15MB.
On Aug 29, 2007, at 04:01, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Dan Janowski <[EMAIL PROTECTED]> wrote:
>
>> What I need now is a few concise examples that have b
tests, you may be able to try it with your
apps, in a development sandbox.
Please post feedback, if you test, what you test, how it went, etc.
so I know if it is getting some eval.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http
ruby_xml_*_free, the memory management is completely different.
Everything is GC friendly and one xmlNode will only have one ruby
VALUE object associated with it at a time.
Dan
On Aug 29, 2007, at 14:31, Charlie Savage wrote:
> Dan,
>
> If you have a second, could you fix the
d increase the coverage of MEM2 as well as
integrating the tests in rwtest into the rake file.
This release of MEM2 resolves a wide variety of bugs.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
libxml at rubyforge (http://rubyforge.org/projects/libxml/)
A new packaged development release from the MEM2 branch (New Memory
Model) is available:
http://rubyforge.org/frs/?group_id=494&release_id=14142
Release notes at:
http://rubyforge.org/frs/shownotes.php?release_id=14142
Ross,
Try this again with the patch release just announced.
Dan
On Aug 31, 2007, at 08:54, Ross Bamford wrote:
> On Thu, 30 Aug 2007 14:41:16 +0100, Dan Janowski <[EMAIL PROTECTED]>
> wrote:
>
>> libxml at rubyforge (http://rubyforge.org/projects/libxml/) now has a
&g
was an issue in copy_bug2.rb in the xpath find that did not
yield the hoped result, so I modified it to find the aaa nodes.
Do an svn update on the MEM2 branch to try it (not released).
Dan
On Sep 3, 2007, at 12:24, Ross Bamford wrote:
> Hi,
>
> On Fri, 31 Aug 2007 16:53:52 +0
touches memory management be
discussed first so as to not create problems, since my activity is
through the entire code base.
Dan
On Sep 2, 2007, at 22:29, TRANS wrote:
> On 8/30/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> libxml at rubyforge (http://rubyforge.org/projects/lib
trees? This may
break even more things though.
The copy feature when a node is a non-doc root, could be made
optional. Either way the behavior changes. Should there be a warning?
Dan
On Sep 4, 2007, at 09:04, Dan Janowski wrote:
> Aah, the << operator. I make a note in the code whe
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
libxml at rubyforge (http://rubyforge.org/projects/libxml/)
A new packaged development release from the MEM2 branch (New Memory
Model) is available:
http://rubyforge.org/frs/?group_id=494&release_id=14239
Subversion tag available at (use svn checkout):
http://libxml.rubyforge.org/svn/tags/MEM2-
On Sep 6, 2007, at 21:20, TRANS wrote:
> On 9/5/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> libxml at rubyforge (http://rubyforge.org/projects/libxml/)
>>
>> A new packaged development release from the MEM2 branch (New Memory
>> Model) is available:
>>
have come along at a good time, because most of us have been
suffering with these memory problems for a long time.
Dan
On Sep 6, 2007, at 20:22, Christopher J. Bottaro wrote:
> On 9/5/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> libxml at rubyforge (http://rubyforge.org/
On Sep 7, 2007, at 15:33, TRANS wrote:
I pitched the idea of compensating Dan for his efforts and my boss
said maybe. Dunno though, they are pretty tight around here.
Oh... okay, well Dan is obviously reading this, but be sure to ask him
directly too. It was just a suggestion on my part
This is either your compiler tools, or there is something drastically
different with the libxml2-devel you have. Check the xmlreader.h from
libxml2 and see if the enum xmlTextReaderMode is defined or changed
from the stable libxml.
Dan
On Sep 12, 2007, at 18:49, Jason Lee wrote:
> Hi
It appears you do not have iconv installed.
Dan
On Sep 12, 2007, at 22:26, Charlie Caroff wrote:
> Hi, I am running FreeBSD 6.2, and am trying to install libxml 0.5.1
> for Ruby. When I run gem install, here is the error I get:
>
> gcc -I. -I. -I/usr/local/lib/ruby/1.8/i386-f
Your libxml2 is 3 years old and a minor rev back. Chances are it is
just too old. You have 2.5.10, libxml2 is at 2.6.30 as of august. Try
a build with a current release of libxml2.
Dan
On Sep 13, 2007, at 19:31, Jason Lee wrote:
> xmlreader.h did not have that enum. This is the rpm i
You can build libxml on its own (i.e. from source with a --prefix to
an out of the way directory) in another location and link to it. If
you do not use a common location like /usr/local then nothing is
going to find it by mistake. You'll just have to make sure the rake
build finds it.
top of the
list at the
moment.
Dan
On Sep 20, 2007, at 13:21, Calvin Bascom wrote:
> I'm using the XML::Parser to parse XML data passed in as a string.
> The
> parse works fine and my code then goes on to access elements and
> attributes in the resulting document. If I use
, I'll roll it into a release.
Get it here:
svn checkout http://libxml.rubyforge.org/svn/branches/MEM2
You should end up with rev 183 or higher.
Dan
On Sep 20, 2007, at 13:21, Calvin Bascom wrote:
> I'm using the XML::Parser to parse XML data passed in as a string.
> The
&g
AP code and the XML document something I can add to svn in
rwtest or does it need to stay private?
Dan
On Sep 21, 2007, at 10:31, Calvin Bascom wrote:
> I am still getting a segfault with these changes, but not the same
> one. It is segfaulting on the line just previ
pdate should yield #187. Give it a try
(one more time).
Hopeful you will report all clear.
Dan
On Sep 21, 2007, at 13:38, Calvin Bascom wrote:
> Dan,
>
> The TAP code I pasted in the original email is fine to use for a
> test case. As far as the XML document, let me create a small
parser is the next thing I will fix. It has some
particularly concerning code in it and would not be surprised if this
is from that.
Dan
On Sep 21, 2007, at 20:39, Calvin Bascom wrote:
> Dan,
>
> This one occurs even less frequently than the last one, but
> unfortunately it sti
Calvin,
If you can produce a test case then I can find the problem.
XML::Document.file is just
a pass through for XML::Parser.
Dan
On Sep 23, 2007, at 17:18, Calvin Bascom wrote:
> Dan,
>
> I am only working with libxml through the TAP class. It is a
> single XML
> docume
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@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml
. 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 t
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'
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: ma
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:
>
> req
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
updated).
Dan
On Oct 26, 2007, at 12:26, mortee wrote:
>
> 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 "m
I am only aware of one instance ([] operator missing on
XPath::Object) that is an interface change. All the other changes are
intrinsically necessary to fix the bugs in the implementation. What
are you dependent on that has changed?
Dan
On Nov 4, 2007, at 13:59, Erik Hollensbe wrote
Reader is a feature yet to be updated. The [BUG] is working as
intended, mostly because I was unsure if anything could do what you
have done. I have not used expand, so I will have to look at it. In
all likelihood it should be an easy fix.
Dan
On Nov 4, 2007, at 16:27, Adam Nelson wrote
just be t1=Time.now, etc) to identify where
the delay is.
Dan
On Nov 7, 2007, at 13:49, mortee wrote:
> I just set out to do some simple measurements to see how fast
> libxml may
> be compared to hpricot.
>
> I made a little script with a ~4 megs XML document appended af
convention, there should be no problem in relocating it
to something else.
Dan
On Nov 13, 2007, at 11:49, Trans wrote:
> Dan,
>
> I want to bring MEM2 over to trunk. I know you believe in working in
> branches. That's good of course, but I'm not sure we have enough
> develop
T.
MEM2 is now fully merged into trunk by an actual svn merge. I can't
say I am overly impressed with svn's merge, mercurial has it better.
I will work in the trunk going forward unless I have to work on
something dangerous.
Dan
On Nov 13, 2007, at 11:49, Trans wrote:
> Dan,
'trunk' for your use.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
This is fixed in the trunk version 210.
Dan
On Nov 4, 2007, at 16:27, Adam Nelson wrote:
> I'm using libxml-ruby 0.5.2 on Ubuntu 7.10 x64 with Ruby 1.8.6. I'm
> trying to use the XML::Reader method expand to extract a full
> XML::Node object when I find one my program is i
Did you have a location for the delay?
On Nov 7, 2007, at 13:49, mortee wrote:
> I just set out to do some simple measurements to see how fast
> libxml may
> be compared to hpricot.
>
> I made a little script with a ~4 megs XML document appended after
> __END__.
>
> $ uname -s
> CYGWIN_NT-5.1
[] operator added to XPath::Object in svn trunk.
On Nov 5, 2007, at 02:35, Erik Hollensbe wrote:
>
> On Nov 4, 2007, at 5:07 PM, Dan Janowski wrote:
>
>> I am only aware of one instance ([] operator missing on
>> XPath::Object) that is an interface change. All
(This is really old, but ...)
Node#new_text added at trunk version #211.
Dan
On May 1, 2007, at 18:00, Eric Schultz wrote:
> Hi everyone,
>
>
>
> I’ve been working on using the libxml-ruby for a project and I
> discovered there’s not an easy way to create a new text node.
Not yet, but it will be shortly. I am dealing with a seg fault now. A
few more days?
Dan
On Nov 16, 2007, at 13:15, mortee wrote:
> Dan Janowski wrote:
>> To do this, please send a sample xml document and ruby code using
>> libxml that illustrates the problem clearly and (hopef
I have just updated the SVN version of libxsl so that it is
compatible with libxml 0.5.2.1, in theory. I don't use it, so if
someone who does wants to try it, please let me know.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
There is a 0.5.2.1 that fixes a problem with xpath.find returns when
they are empty. That is only available by an svn checkout, soon to be
released as a gem. It is easy to build and after the pkg/ dir will
have a gem that you can install.
Dan
On Nov 16, 2007, at 17:17, uncle wrote:
>
Are we then talking about:
ext/xml
ext/xsl
?
On Nov 25, 2007, at 08:27, Trans wrote:
>
>
> On Nov 24, 1:03 pm, Sean Chittenden <[EMAIL PROTECTED]> wrote:
>>> Ok. Thanks. I'll have to move to ext/xsl/ then... hmm..actually
>>> if we
>>> want to keep it in xml/ then we'd have to make two layers
LoadError (i think) if it cannot, since all document objects are
dependent on libxml.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
issues which stand between here and
the next release is:
1. correct find operation with namespaces
2. wall-clock delay when using Reader
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
interrogating the variable is not correct, the functionality
should be. Does the DTD entity loading work when you set it?
The correction is committed in svn #216
Dan
On Nov 26, 2007, at 16:18, Paul Dlug wrote:
> It doesn't appear to me that the flag on XML::Parser
> 'default_load_ext
eally want to use doc.dump.
Encoding has never worked correctly within the library. It only
functions properly when fed UTF-8 as I have had to employ Iconv for
anything else.
Dan
On Nov 26, 2007, at 16:05, Tim Perrett wrote:
> Hey Chaps
>
> There seems to be some kind of issue with U
(I had not previously modified
this code), now it is less broken.
Dan
On Nov 26, 2007, at 22:38, Dan Janowski wrote:
> I don't have 0.3x on my system anymore, but I do not think UTF16 will
> behave any differently. .to_s is written incorrectly, from what I can
> tell, since it just f
Last night I could not see what could BE and LE stand for?! Well, of
course, Big Endian and Little Endian. When there is no lead in to
indicate, the encoding can specify.
Dan
On Nov 27, 2007, at 05:08, Tim Perrett wrote:
>> A few other notes about UTF-16 specifically; UTF-16 will res
ely enough at this code segment when I
encapsulated the the namespace recursion. Thanks for the patch. You
have credit in the svn log.
Dan
On Nov 27, 2007, at 08:39, keisuke fukuda wrote:
> So, this should be the patch.
>
> Index: ext/x
The method mapping was transposed and is fixed in svn #220
See if that works now.
Dan
On Nov 27, 2007, at 10:17, Paul Dlug wrote:
>
> On Nov 26, 2007, at 9:34 PM, Dan Janowski wrote:
>
>> Hi,
>>
>> You are at least half correct. xmlSubstituteEntitiesDefaultValue ha
make a recommendation.
Dan
On Nov 27, 2007, at 11:41, Paul Dlug wrote:
There is a serious inconsistency when "round tripping" XML containing
UTF-8 characters. If you output the document to a string after parsing
you get the UTF-8 back out, if you just grab a node and convert to a
stri
I see the merit in this kind of approach but it cannot conflict with
the libxml work flow. I.e.:
instead of XML::Document.parse(xml) => Document
XML::Parser.parse(xml) => Document
If you want to update the patch for the current code base, I am
willing to apply and eval it.
Dan
On
Please send a full script and data so I can try to reproduce the
problem. i.e. your xml-bm-libxml.rb script.
Dan
On Nov 28, 2007, at 08:45, mortee wrote:
> I've posted what I've found out. Do you have any idea of a cause/
> solution?
>
> mortee
>
> Trans wrote:
I have not been able to reproduce this SEGV on two different
processor architectures. Any additional effort or debugging would be
necessary.
Yes, _private is for application use.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http
svn #221 catches this problem now. There are a variety of ways to
seed the parser, not sure there is a preferred way.
Dan
On Dec 3, 2007, at 11:54, Christopher J. Bottaro wrote:
> Hello,
>
> This code segment segfaults:
>
> p = XML::Parser.new
> p.string = ''
>
. Have any interest in contributing more?
Dan
On Dec 3, 2007, at 14:52, Paul Dlug wrote:
> Dan,
>
> Just wondering, any feedback on this?
>
>
> Thanks,
> Paul
>
> On Nov 27, 2007, at 11:41 PM, Paul Dlug wrote:
>
>>
>> On Nov 27, 2007, at 3:26 PM, Dan Jano
mkmf) that is unlikely.
At the beginning of extconf.rb, put this to inspect the library paths
and see if it includes the ruby base installation:
$stderr.puts $LOAD_PATH.inspect
I have no idea why it would or might be getting blown.
Dan
On Dec 7, 2007, at 09:33, [EMAIL PROTECTED] wrote:
>
reformulated feature/bug
tasks we we can manage to get it done. It is also the right place to
be attaching patches and requirements. I am starting to loose track of
it.
Thanks to everyone for your efforts and thoughts.
Dan
On Dec 9, 2007, at 04:30, Jochen Topf wrote:
>
> On Fri,
Keisuke,
I just modified and added in the groups. There is pre-0.5 for all the
old stuff and 0.5 for current issues. There is also a catagory
'memory' for issues relating to SEGV and such.
I am open to all suggestions on other categories or ways to improved
the bug stream.
D
What does the mkmf.log contain?
On Dec 16, 2007, at 22:18, Henry Wagner wrote:
> Hi,
>
> I'm running into some errors installing libxml-ruby on OS X 10.3.9.
> I'm using ruby 1.8.6
>
> Gonk:~/Desktop apple$ sudo gem install -r libxml-ruby
> Building native extensions. This could take a while...
>
Depends on the version you are running.
ruby -e 'require "xml/libxml"; puts XML::Parser::VERSION'
On Dec 17, 2007, at 18:47, [EMAIL PROTECTED] wrote:
> Hi,
>
> I have an application that reads a listing of files from a
> directory, and then uses libxml-ruby (using XPath) to parse the
> files
Maybe it is a rather old version of libxml2.
On Dec 17, 2007, at 21:38, Henry Wagner wrote:
> I made some progress. I didn't have gcc installed on the machine. Now
> I get further but still have trouble. I've attached mkmf.log
>
> Henry
>
> On 12/17/07, Dan Janows
That version has all of the really bad leaks taken care of. There is a
more recent version in SVN, but it is not in an RC state, which may be
a few more days. It has a few more fixes, including some to XPath.
I'll announce the update, hopefully soon.
Dan
On Dec 18, 2007, at 08:49, [
mlsoft.org/xmllint.html
Dan
On Jan 7, 2008, at 01:14, GlennNZ wrote:
> I'm following through the w3schools tutorial on xsd and xml validation
> and I'm trying to get one of the examples to validate. The problem
> seems to be in validating the attributes because if I strip
than double-free, so it may be that the memory is being stomped on by
something else.
I have no insight. Please post what you can to get to the bottom of it.
Dan
On Jan 11, 2008, at 13:57, Marc Munro wrote:
> My last experience with ruby and valgrind was kinda unpleasant. Maybe
> with ru
o the illustrative details will increase the chances of
implementation.
Dan
Tracker is here:
http://rubyforge.org/tracker/?atid=1974&group_id=494&func=browse
On Jan 13, 2008, at 19:24, GlennNZ wrote:
>> From looking at the api I'm guessing that the xmllib ruby bindings
?
Dan
On Jan 14, 2008, at 18:56, Marc Munro wrote:
> It's beginning to look as though something in one of my xml documents
> has been removed part-way through my use of it.
>
> I am trying to discover exactly what is happening but I have a
> question
> about how ruby and C
Please send me a documentation paragraph that I can add to .find which
makes this more explicit and understandable. Hopefully this will
eliminate future confusion over the usage.
Thanks,
Dan
--
Dan Janowski
[EMAIL PROTECTED]
On Jan 15, 2008, at 10:46, Steven Parkes wrote:
> I ended
trans has changed the build system and the organization to deal with
the libxslt issues and rake muck. The builder is task/setup, the more
detailed tasks require you to install ratch.
Dan
On Jan 21, 2008, at 5:50 PM, Steven Parkes wrote:
> Am I the only one, or is the trunk kinda bro
Hi Sam,
Thank you for tracking these changes. In the interest of tracking all
changes so they may be properly applied, please submit this to the
patch tracker at this location:
http://rubyforge.org/tracker/?func=add&group_id=494&atid=1973
Dan
On Jan 31, 2008, at 10:15, Sam Ru
apply consistent and productive
time slices for continuing work on the code base. If you find a
problem with anything said here or something omitted, please discuss.
Dan
___
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org
ng to do it under MRI. Then I have this shimmering vision of
dumping the whole code base and just writing an FFI interface.
Dan
On Jan 31, 2008, at 10:51, pat eyler wrote:
> has anyone done any work getting libxml to work on/with Rubinius?
>
> --
>
Never liked it much myself.
Dan
On Feb 1, 2008, at 16:29, Trans wrote:
> I think we may want to change the package name from 'libxml-ruby' to
> just 'libxml'. The reason I suggest this is b/c, while it might
> suffice as is, it's confusing in light of platf
Are you sure it is the doc reference and not the GC finalizers
running? Put a print statement after it and see what happens.
Dan
On Feb 6, 2008, at 17:11, Saurabh Nanda wrote:
> Why does the following code always cause a segfault on the last
> statement, when simply trying to refer t
A double free on the context seems the likely candidate. If you can
send a bug exploit that I can reproduce then there is a possibility of
resolution. The stack trace is identification.
Dan
On Feb 5, 2008, at 10:20, Saurabh Nanda wrote:
> I have a long running RESTful web service t
C sure is lovely, isn't it. I will try to reproduce this. If you would
not mind, please post this as a bug so I can track it at:
http://rubyforge.org/tracker/?atid=1971&group_id=494&func=browse
Dan
On Feb 7, 2008, at 03:36, Saurabh Nanda wrote:
>> Are you sure it is th
Glad you found that. I would like to make a release, but I am not sure
of the finality of the build system changes. As soon as there is a
read on that, I will bundle and release.
Dan
On Feb 7, 2008, at 12:48, Luc Heinrich wrote:
> On 7 févr. 08, at 17:27, Luc Heinrich wrote:
>
&g
Since it is OS X, did you try to enable any of the malloc debug (man
malloc)? There are a whole bunch of env vars that can be set, sometimes they
provide useful information.
Dan
On Feb 9, 2008 12:37 PM, Luc Heinrich <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> So my last posts a
Have not yet. Looking for time. I appreciate your checking.
Dan
On Feb 9, 2008, at 12:52, Sam Ruby wrote:
> Sam Ruby wrote:
>> Dan Janowski wrote:
>>> Hi Sam,
>>>
>>> Thank you for tracking these changes. In the interest of tracking
>>> all
>&g
My experience is that -core is not very helpful and it may well sound
like any number of other complaints they have received. I have my
doubts there is anything they can really offer.
Dan
> Hey Dan, what do you think of forwarding this to ruby-core mailing
> list? I'm suspect the
-ruby is excellent.
Of course it will break continuity with the gem
history. Should we be using the 2 in libxml2 to
mirror the tie more literally?
As for the XML namespace, that can be done
easily and compatibly by offering an include
that equates the XML const with the LibXML
const. We can also f
number of people using this library and the number of issues with it are too
much for a single developer needing to make a living.
Dan
On 5/26/08, Marc Munro <[EMAIL PROTECTED]> wrote:
>
> I'm curious about the development status of libxml.
>
> My application still core
em. I would love to get
>> libxml-ruby working again. A lot of my projects will depend on it.
>>
>> Dan, how can other people help? Is there someone who can coordinate
>> other people's efforts in the right direction?
>>
>
>
> Sean's Posit #6: The group
1 - 100 of 106 matches
Mail list logo
