On Fri, Jul 11, 2008 at 9:41 AM, Sean Chittenden <[EMAIL PROTECTED]> wrote:
>>> I'm not entirely opposed to the idea... but am curious for some example
>>> functions. :) -sc
>>
>> XML::Parser.register_error_handler could be implemented in ruby.
>> ruby_xml_attr_not_type_name() could be implemente
I'm not entirely opposed to the idea... but am curious for some
example
functions. :) -sc
XML::Parser.register_error_handler could be implemented in ruby.
ruby_xml_attr_not_type_name() could be implemented in ruby.
All of the rb_define_consts in ruby_xml_node.c
ruby_xml_node_set_xpath_get(
On Fri, Jul 11, 2008 at 8:52 AM, Sean Chittenden <[EMAIL PROTECTED]> wrote:
>> As I've started reading through the libxml-ruby code, I have run
>> across methods implemented in C that could be implemented in Ruby. I
>> would like to change them to be implemented in Ruby. Is anyone
>> opposed to t
On Fri, Jul 11, 2008 at 8:52 AM, Sean Chittenden <[EMAIL PROTECTED]> wrote:
>> As I've started reading through the libxml-ruby code, I have run
>> across methods implemented in C that could be implemented in Ruby. I
>> would like to change them to be implemented in Ruby. Is anyone
>> opposed to t
As I've started reading through the libxml-ruby code, I have run
across methods implemented in C that could be implemented in Ruby. I
would like to change them to be implemented in Ruby. Is anyone
opposed to that? I think it would make coding easier, less buggy, and
more fun!
I'm not entirel
