I have a strange situation where the code:
c = Class.new { eval parser }
... works in IRB (ruby 1.9.3) but not in code. I've tried it with and without 'class Foo' wrapping my methods. This is frustrating, to say the least. I can copy the string parser's content directly into variable parser in irb, and then create the class using the above line and my methods are all there but when I do it in code, they aren't.
C = Class.new
C.class_eval(code)
...Works for me in Ruby 1.9.2, even when saved in a file. Can you try and see if it works in 1.9.3?
code fetchclass = Class.new fetchclass.class_eval( parser ) puts fetchclass.instance_methods.to_s ## doesn't show my methods inst = fetchclass.new( @db ) # crashes code Or, should I include the entire class def in the string including class Foo?
I've solved it.
The situation was that I was dynamically creating the definitions in order to make an optimized parser, and I was building it using incrementally added strings. As you can imagine, there was a lot of quote-escaping involved, especially with the MySQL queries. When I tested in irb, I forgot that using
puts parser
... evaluated the string while printing, removing one level of escaping while doing so.
The solution was simple: eval my string before class_eval'ing it.
fetchclass = Object.const_set(
characteristics['shortname'],
Class.new { class_eval( eval parser ) } )
initialize': wrong number of arguments(1 for 0) (ArgumentError) from /home/devel/recc_ruby_mysql/ruby/Content/FetcherBuilder.rb:154:innew'codefetchclass = Class.new { eval parser } inst = fetchclass.new( @db ) puts inst.instance_variables.to_scode