# Reek 1.0.0 released **URL:** \ **Category:** Ruby\ **Created:** [April 5, 2009, 3:39pm UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768 "2009-04-05T15:39:20Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 5, 2009, 3:39pm UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/1 "2009-04-05T15:39:20Z")
Hi, Reek version 1.0.0 has been released! Reek detects smells in Ruby code. It can be used as a stand-alone command, or as a Rake task, or as an expectation in Rspec examples. ## Changes in this release: ### Major enhancements: - Use \*.reek files in source tree to configure Reek’s behaviour - Added -f option to configure report format - –sort\_order replaced by -f, -c and -s - Matchers provided for rspec; eg. foo.should\_not reek ### Minor enhancements: - Smells in singleton methods are now analysed - Uncommunicative parameter names in blocks now reported - Modules and blocks now reflected in scope of smell reports ### Fixes: - Corrected false reports of long arg lists to yield - A method can now be a UtilityFunction only when it includes a call ## More information: - [http://wiki.github.com/kevinrutherford/reek](http://wiki.github.com/kevinrutherford/reek) - [http://reek.rubyforge.org/rdoc/](http://reek.rubyforge.org/rdoc/) Cheers, Kevin ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 7, 2009, 8:24am UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/2 "2009-04-07T08:24:45Z")
On Apr 5, 2009, at 06:37 , Kevin Rutherford wrote: > Hi, > Reek version 1.0.0 has been released! > > Reek detects smells in Ruby code. It can be used as a stand-alone > command, or as a Rake task, or as an expectation in Rspec examples. congrats! You should test reek against ruby\_parser and make sure it holds up for you. You might want to look at my project gauntlet for that (see the gauntlet plugin that ships with ruby\_parser). ParseTree is going to go away… you should prepare for that. ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 7, 2009, 11:28am UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/3 "2009-04-07T11:28:13Z")
> You should test reek against ruby\_parser and make sure it holds up for you. > You might want to look at my project gauntlet for that (see the gauntlet > plugin that ships with ruby\_parser). > > ParseTree is going to go away… you should prepare for that. Ok, thanks for the warning. Do you know when it will go away? Cheers, Kevin ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 8, 2009, 11:04am UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/4 "2009-04-08T11:04:43Z")
On Apr 7, 2009, at 02:26 , Kevin Rutherford wrote: > > You should test reek against ruby\_parser and make sure it holds up > > for you. > > You might want to look at my project gauntlet for that (see the > > gauntlet > > plugin that ships with ruby\_parser). > > > > ParseTree is going to go away… you should prepare for that. > > Ok, thanks for the warning. Do you know when it will go away? Officially, it’ll end of life when 1.8 does… when that is I have no idea. That said, I’ve done NOTHING to check compatibility against 1.8.7 or the upcoming 1.8.8 and don’t even have it on my radar right now. ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 20, 2009, 10:45pm UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/5 "2009-04-20T22:45:46Z")
Hi Ryan, > You should test reek against ruby\_parser and make sure it holds up for you. > You might want to look at my project gauntlet for that (see the gauntlet > plugin that ships with ruby\_parser). ParseTree will create a parse tree for any object; right now, I can’t see how to do that with ruby\_parser – is it possible? Thanks, Kevin ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 21, 2009, 5:47pm UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/6 "2009-04-21T17:47:21Z")
On Apr 20, 2009, at 14:06 , Kevin Rutherford wrote: > > > ParseTree will create a parse tree for any object; right now, I > > > can’t > > > see how to do that with ruby\_parser – is it possible? > > > > nope. > > Is it planned? nope. not possible in ruby 1.9. ---
**Author:** ![Kevin\_Rutherford](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/c4cdca/32.png) [@Kevin\_Rutherford](https://www.ruby-forum.com/u/Kevin_Rutherford)\ **Post date:** [April 20, 2009, 11:01pm UTC](https://www.ruby-forum.com/t/reek-1-0-0-released/164768/7 "2009-04-20T23:01:37Z")
On Apr 20, 2009, at 13:45 , Kevin Rutherford wrote: > ParseTree will create a parse tree for any object; right now, I can’t > see how to do that with ruby\_parser – is it possible? nope.