(Sorry if this double posts, my email version didn't seem to get thru.) On Jul 15, 3:26 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: > Its a clever idea. But I'm not convinced because I really don't like the > extra include. Why exactly would I want to mixin libxml into my own classes > or modules - just to make coding a bit easier doesn't seem enough > justification?
It strikes me as a bit funny that "good practice" seems cleaver :-) I know it may seems inconvenient, but it is worth it. Moreover, there is a simple solution to achieving the effect you want (though I would discourage it in any code you intend to be reusable by others). Just use: require 'libxml/xml' Were libxml/xml.rb is simply require 'libxml' include LibXML > I'd just as soon do this: > > XML = LibXML > > And be done with it. I agree you could do this though: > > XML = LibXML::XML > > Um, are you really tied to this idea? Going through and changing everything > again sounds really uninteresting. Please? T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
