Error: Tried to use object of type Class (14) as type String (48) #151

Closed
harukizaemon opened this Issue Jan 6, 2010 · 2 comments

Comments

Projects
None yet
2 participants

This worked in rc1 (and works fine in MRI 1.9 and 1.8.7)

> rake spec
(in /Users/haruki_zaemon/Projects/hamster)
rake aborted!
  Tried to use object of type Class (14) as type String (48)
/Users/haruki_zaemon/Projects/hamster/rakefile:1:in `__script__'
kernel/common/compiled_method.rb:230:in `as_script'
kernel/delta/requirer.rb:260:in `single_load'
kernel/delta/requirer.rb:98:in `unified_load'
kernel/common/kernel.rb:675:in `load'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile {}'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2000:in `run {}'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/haruki_zaemon/.rvm/gems/rbx-1.0.0-rc2/gems/rake-0.8.7/bin/rake:31:in `__script__'
kernel/common/compiled_method.rb:230:in `as_script'
kernel/delta/requirer.rb:260:in `single_load'
kernel/delta/requirer.rb:98:in `unified_load'
kernel/common/kernel.rb:675:in `load'
/Users/haruki_zaemon/.rvm/rbx-1.0.0-rc2/bin/rake:22:in `__script__'
kernel/common/compiled_method.rb:230:in `as_script'
kernel/delta/requirer.rb:260:in `single_load'
kernel/delta/requirer.rb:345:in `load_from_extension'
kernel/loader.rb:413:in `script'
kernel/loader.rb:522:in `main'
kernel/loader.rb:526:in `__script__'

Solution: find . -iname '*.rbc' -exec rm {} ;

Owner

evanphx commented Jan 7, 2010

Ok, great.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment