# Flog 2.1.2 Released

**URL:** <https://www.ruby-forum.com/t/flog-2-1-2-released/170942>\
**Category:** Ruby\
**Created:** [June 24, 2009, 10:18am UTC](https://www.ruby-forum.com/t/flog-2-1-2-released/170942 "2009-06-24T10:18:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [June 24, 2009, 10:18am UTC](https://www.ruby-forum.com/t/flog-2-1-2-released/170942/1 "2009-06-24T10:18:56Z")

</div>

flog version 2.1.2 has been released!

- [http://ruby.sadi.st/](http://ruby.sadi.st/)
- [http://rubyforge.org/projects/seattlerb](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:

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [August 3, 2009, 6:29pm UTC](https://www.ruby-forum.com/t/flog-2-1-2-released/170942/2 "2009-08-03T18:29:39Z")

</div>

On Wed, Jun 24, 2009 at 3:17 AM, Ryan D.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)wrote:

> flog version 2.1.2 has been released!

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://groups.google.com/group/rubyonrails-talk/browse_thread/thread/8e7ba74ea6ba58a1)  
[http://railsforum.com/viewtopic.php?id=32954](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)'.

---

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [October 30, 2009, 5:06pm UTC](https://www.ruby-forum.com/t/flog-2-1-2-released/170942/3 "2009-10-30T17:06:29Z")

</div>

> 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