Maybe I missed something, but doc.encoding takes/returns a number
instead of an encoding string. not sure how that change from 0.8.x
happens.
On Mar 9, 2009, at 13:54, Charlie Savage wrote:
Well, that didn't last quite as long as I had hoped.
A new version of libxml-ruby, version 1.1.0, is
You may be able to produce what you want by defining a module and
extending the Document with it:
ardent:~ danj$ irb
irb(main):001:0> class A
irb(main):002:1> end
=> nil
irb(main):003:0> module B
irb(main):004:1> def hello
irb(main):005:2> puts "hello"
irb(main):006:2> end
irb(main):007:1> end
I did this for compatibility. Set is clearly just a pass through to
Object. I cannot recall if there is something that expects identity in
is_a?.
Dan
On Jul 13, 2008, at 22:09, Charlie Savage wrote:
Looking through the xpath code, there is a class XML::Node::Set that
seems fairly pointles
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
On Jul 3, 2008, at 14:01, Sean Chittenden wrote:
Before we do that though I was wondering what others thought
about of
switching to Git?
Well, I know git is the new cool think in town. But I'm on
Windows, and
love TortoiseSvn, so I don't have any motivation to move to git
(lousy
window
n anything else.
That was the single largest problem which should be resolved. The
issues that remain are as yet undefined.
Comments, answers?
__
Marc
On Tue, 2008-05-27 at 11:43 -0400, Dan Janowski wrote:
The intersection is a null set. The best hope may be rubinius where
the extensions
The intersection is a null set. The best hope may be rubinius where the
extensions can be written in ruby. Fixing the memory model for nodes and
documents made a big difference, but the problems that are lingering are
elusive and compounded by ruby's obsficating GC. I put a lot of time into
it, but
I have been unable to continue work, my personal life not allowing. However,
the amount of effort that I have put into this has not cleared the library
of all its problems and it really needs active shared involvement of more
than just a single developer. This is sort of asking for manna, but the
n
On Sun, 6 Apr 2008 15:51:40 -0700 (PDT)
Trans <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm going to make a new release with the minor fixes I mentioned
> earlier.
>
> I would also like us to consider these changes:
>
> 1) Rename 'libxml_so' to 'libxmlc'.
>
> 2) Rename the package from 'libxml-ruby
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 best input
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
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 about crashes in 'r
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:
>
>> So it seems
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 the doc reference and not
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 that needs
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 to 'doc'? T
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 platform gems. Ie. the "-
> ruby" looks lik
This entices me. The MRI internals (esp. the GC) are the biggest
obstacle to making this library work and I am beginning to really hate
them. I've even had this delusion that making this library work with
Subtend may enable effective repair of outstanding faults more easily
than trying to d
My thanks to all of you for using, discussing, reporting and
contributing to the ruby-libxml extension. As more people become
involved and as the quantity of contributions and issues grows, it has
become more difficult to keep track of what needs to be done. With
this in mind, the following
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 Ruby wrote:
> S
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 broken? ext
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
The basics are there. The XSLT extension tracks the ruby document peer
that it is working against. The XSLT mark() marks the document peer,
which should retain the reference. XPath returns node sets and those
nodes reference their parent doucment, so when the GC runs, the
Document is marked
I'm not sure if this is a missing feature or a bug, but please
register a feature request and include attachments, scripts and
commands that you expect to work with an explicit illustration of what
is missing and what it should look like. I am unfamiliar with the DTD
handling, so the illust
Marc,
I have yet to have valgrind produce anything meaningful in debugging
this environment. I have tried the suppressions, but alas, nothing. If
someone can offer an effective way of using it, I am quite interested.
As for this bug, the context code is pretty simple. This is different
than
Please verify your validation results using the libxml2 included
binaries, in this case 'xmllint'. There has been no recent work on the
validation pass through, which is the same as saying I do not know if
the ruby library has any culpability. Thus, try the xmlsoft tools.
http://xmlsoft.org/
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, [EMAIL PRO
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
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
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...
>
an
On Dec 10, 2007, at 07:41, keisuke fukuda wrote:
Hi,
2007/12/9, Dan Janowski <[EMAIL PROTECTED]>:
Which forks me to another topic, we need to eval and clean up the
task
list on rubyforge and seed it with new or reformulated feature/bug
tasks we we can manage to get it done. It i
I have not looked at the IO interfaces for this library, but it seems
clear that there should be a good way of passing, or using, a ruby IO
stream as a source to the SAX parser.
Which forks me to another topic, we need to eval and clean up the task
list on rubyforge and seed it with new or r
mkmf is a core part of ruby and should be part of the base
installation. First make sure it is there. In irb, do a require of
'mkmf' and make sure it results in true. If not, then your ruby
install is somehow messed up. However, if you have installed any other
gems (they all use mkmf) that
. 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
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 = ''
> p.parse
>
> I'm using revision 2
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://ru
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:
>> mortee, do you think you can
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 Nov 27, 2
The handling of encoding is not coherent in the extension, as my last
patch on the topic illustrates. While I have no doubt that there are
issues to resolve, in this particular instance I do not get the
result you do.
Anyone wanting to look at the way encoding is handled is welcome to
mak
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
Patch applied, svn #219. Note that 'p' of the .find result will not
result in the xml segment that it used to in 0.3.8. The .find now
returns an XPath::Object type and it has no to_s method defined. You
can get the same effect by using .to_a on XPath::Object.
I had not looked closely enough
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 result in
(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
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 feeds the encoding of the document back into the
formatter. But in either case, if you want the as-encoded document,
you really wan
Hi,
You are at least half correct. xmlSubstituteEntitiesDefaultValue has
nothing to do with DTD. However, while the _get method you have
illustrated here makes reference to the wrong variable, the _set
method does not suffer the same problem. So, while the script return
value interrogatin
The SVN repository now includes version 0.5.2.2 (as of #212) that
fixes a major problem with .find expressions which return non-nodeset
results like a boolean, string or number. This seems to fix the only
remaining memory fault (segv) that I am aware of.
The only two outstanding service issu
On Nov 26, 2007, at 11:02, Sean Chittenden wrote:
>> Are we then talking about:
>>
>> ext/xml
>> ext/xsl
>>
>>> Really? Damn. I thought you had suggested we make one package out of
>>> it, and I was coming around to that idea.
>
>
> Hrm... I think I was advocating for a single repo, but not singl
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
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:
> I jus
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
http://ru
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
(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. Since
> I needed t
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 interested in. This
>
All changes developed in the MEM2 branch have been merged back into
trunk. The trunk release version is unchanged (0.5.2.1) as of the
merge. Changes, patches, upgrades will be in the trunk until further
notice. In other words, for those of you getting updates via SVN, be
sure to check out '
[] 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
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
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,
>
> I want to
I meant to work on this over the weekend, but I have been a bit under
the weather. Let me look at it to figure out the right way. I know
you suggested to just move trunk to something else and replace it
with MEM2. That may be the best way, since trunk is not required by
svn, just a conventi
The timing info is curious because libxml does the job with very
little cpu time, it is the real-time delay that is the problem.
On identifying the location of the delay (since it is wall-clock time
we are talking about), it should be sufficient to do splits between
each method call (could j
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:
>
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:
>
> O
Hi,
The namespace code within xpath.find is rather oddly written and
struck me as such at the time I was re-writing xpath.find. I had to
leave it alone, as scope expansion during such an operation is
hazardous. Now that you are having trouble with it, maybe I can
figure out what it is supp
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 runni
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
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 u
;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 <[EMAIL PROTECTED]> wrote:
>> XML::XPath::O
he API
> changes?
>
> Thanks.
>
> On 10/10/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> Release 0.5.2 MEM2 release fixes all known and reported memory
>> faults.
>>
>> project page
>>
>> http://rubyfo
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-
es that have been fixed? It creates an extra step of writing
> the
> string (which I retrieve from a rails TempFile object) to an
> intermediate file, but at least I could test to see if the parser is
> causing the problem that way.
>
> Thanks,
> Calvin
>
> Dan Janowski
0x00da529e in rb_load (fname=3082098120, wrap=0) at eval.c:6857
> #254 0x00da5729 in rb_require_safe (fname=3082102840, safe=0) at
> eval.c:7213
> #255 0x00da59c3 in rb_f_require (obj=3086510500, fname=3082105720) at
> eval.c:7106
> #256 0x00d900b8 in call_cfunc (func=0xda59a0
available.
> ) at eval.c:5665
> #222 0x00ccc4dd in rb_call0 (klass=Variable "klass" is not available.
> ) at eval.c:5815
> #223 0x00ccd106 in rb_call (klass=3085835440, recv=3085830560,
> mid=30129, argc=1, argv=0xbfa227a0, scope=1, self=3085830560) at
> eval.c:6062
c:5815
> #229 0x0084d106 in rb_call (klass=3085917360, recv=3085912480,
> mid=30129, argc=1, argv=0xbfcf2270, scope=1, self=3085912480) at
> eval.c:6062
> #230 0x0084923f in rb_eval (self=Variable "self" is not available.
> ) at eval.c:3462
> #231 0x0084b674 in rb_eval (
I have just committed a re-write of XPath/XPointer and *.find (calls
to XPath). It is svn
revision 183. See if it fixes this problem.
Note, there is an incompatibility, the new XPath::Object class does
not support .xpath method, but I could find no reason to carry it
forward.
If it works, I
Hi,
As you suspected, this is the same problem. Your report helps to
confirm my
suspicions. It is the memory handing inside the xpath/node_set
portion of
the extension. I think I have figured out how to solve the problem,
now I just
need an hour to do it. Please bear with me, this is the top
; projects.
>
> Thanks again,
>
> - jason
>
> On 9/13/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> 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
uming there is a baseline lbxm2-devel version, but I couldn't
> find it anywhere.
>
> thx,
> - jason
>
> On 9/12/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>> This is either your compiler tools, or there is something drastically
>> different with the libxml2-
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-freebsd6.2 -I. -I
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 all,
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, I
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/
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 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
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
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
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
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
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
Dan
libxml at rubyforge (http://rubyforge.org/projects/libxml/) now has a
packaged development release from the MEM2 branch (New Memory Model)
http://rubyforge.org/frs/shownotes.php?release_id=14118
The downloads are highlighted here:
http://rubyforge.org/frs/?group_id=494&release_id=14118
Pleas
Charlie,
If they are the ones I am thinking of, they are going away entirely
(no longer needed). If they were in ruby_xml_{node,document,attr}.c,
there are gone now. They will be in modules I have not touched yet,
but they will go too.
There is no code carried forward for ruby_xml_*_new or
Hi all,
I have just committed the current state of my memory overhaul to a
branch MEM2. It is not complete, but it includes rewritten node,
document and attr. I also removed attribute. It does pass the tests
run during rake, so it may be good to try out generally, but I make
no guarantees.
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
Hi all,
I am going to go out on a limb and say, tentatively, that my new
approach to memory management is working. It is so far only applied
to the ruby side of tree.c functions (ruby_xml_node...). My simple
example of creating the same document 1M times, loosing references to
the priors a
My analysis leads me to a similar conclusion. Reference counting is
out and there is no need for it. This is my hypothesis:
If things are being freed unintentionally, then there are not enough
ruby to ruby cross-references to maintain integrity during mark and
sweep. A single ruby object hol
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 second case the version nu
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.
>
> http://web.ar
If it is possible to have both CVS and SVN under the project, then
one option is to get a full historical copy of the libxml CVS repo
and put it into libxml2 and just leave it for reference. Then import
the latest into SVN and just start from there. As long as the logs
are accessible, it ma
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. No one, as far as I know, is ac
ne the maintainer. So that means things fall back to
> Sean Chittenden -- but is he around? I see three other members listed:
>
> Dan Janowski
> Laurent Sansonetti
> Pat Eyler
>
> Are any of you guys around?
>
> I fear there's no one at the hem again, but there are
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
Descr
1 - 100 of 103 matches
Mail list logo
