On Jul 14, 12:34 pm, Charlie Savage <[EMAIL PROTECTED]> wrote:
> > True as well. But I wouldn't say undoable. We can *responsibly*
> > migrate. Or we can take a simpler solution and just wrap everything in
> > LibXML module. Then in libxml.rb:
>
> > include LibXML
>
> Ok - I can agree with that. Done.
>
> > I leave it up to you all to decide what is best. All I ask is that the
> > lib directory at least be called 'libxml'.
>
> Done.
>
> With those changes, I'm going to cut a new 0.7.1 release unless there
> are objections.
He he. Hold on. I think you misunderstood what I mean by "include
LibXML". This is what I was thinking (using document.rb as an
example):
module LibXML
module XML
class Document
...
then in libxml.rb:
include LibXML
so everything will work just as it did before, but there would be an
extra level of namespace. I'm not sure this is the best solution, but
it was the thought.
But since you went ahead with swapping XML => LibXML, that probably
best anyway. I wonder about one thing though, is backward
compatibility best preserved with:
XML = LibXML
or as you have it:
module XML
include LibXML
end
T.
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
