flog version 2.1.2 has been released!
* <http://ruby.sadi.st/>
* <http://rubyforge.org/projects/seattlerb>
Flog reports the most tortured code in an easy to read pain
report. The higher the score, the more pain the code is in.
Changes:
### 2.1.2 / 2009-06-24
* 1 bug fix:
* Fixed dependency spec on ruby_parser. (jan)
Is flog v2.1.2 supposed to work?
$ flog
/Library/Ruby/Gems/1.8/gems/flog-2.1.2/bin/flog:11: undefined method
`flog_files' for #<Flog:0x118b3ec> (NoMethodError)
from /usr/bin/flog:19:in `load'
from /usr/bin/flog:19
$ gem list | grep flog
flog (2.1.2)
Nothing else is interfering with this version of flog, so far as I can tell.
(Y'know, like a github version or anything.)
Seems like I'm not the only one having trouble:
http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/8e7ba74ea6ba58a1
http://railsforum.com/viewtopic.php?id=32954
I started trying to run flog's tests, but I'll admit I gave up after
installing minitest to make it happy, then still needing to ruby -rubygems
the test file to get past that one error, and then running into 'undefined
method `sexp_type' for class `Sexp' (NameError)'.
On Wed, Jun 24, 2009 at 3:17 AM, Ryan Davis <ryand-ruby@zenspider.com>wrote:
flog version 2.1.2 has been released!
--
-yossef
I started trying to run flog's tests, but I'll admit I gave up after
installing minitest to make it happy, then still needing to ruby
-rubygems
the test file to get past that one error, and then running into
'undefined
method `sexp_type' for class `Sexp' (NameError)'.
For me this meant I had an older version of ParseTree gem installed
offending file:
ParseTree-2.2.0/lib/sexp_processor.rb
desired file:
sexp_processor-3.0.3/lib/sexp_processor.rb
so when parse_tree was doing a require 'sexp_processor' it was picking
up this other file instead of the right one.
Fixes might be: uninstall old ParseTree gem, or possibly within
ruby_parser, before the require 'sexp_processor' run gem
'sexp_processor' to make sure it's at the beginning of the search path,
though it's hard to tell because it appears Rubygems loads gem's lib
paths in the order that Dir[] returns them, which is different depending
on the machine you're on and the order they were installed, etc.
HTH.
-r
--
Posted via http://www.ruby-forum.com/.