That's a gem related question, IMHO, but I like that concept best, to
be honest.
require 'libxml'
require 'xml'
Great. That'll work for me too.
I think LibXML::XML::* is rather redundant and a waste of keystrokes,
however, and that it should be LibXML::* and XML::*. $0.02. -sc
Shouldn't need to type all those keystrokes. 99%+ of time you're going
to include LibXML into either the toplevel or one's own module.
Heh. I disagree, actually, or more correctly, my use case has almost
always been different. Most XML processing is done in batch from a
simple script, not inside of an embedded app that does:
class Foo
include LibXML
...
end
Not saying I haven't done that a few times in a few web apps w/ other
modules, but it's less frequent for XML, IMHO. -sc
--
Sean Chittenden
[EMAIL PROTECTED]
_______________________________________________
libxml-devel mailing list
libxml-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/libxml-devel
