Recently in flay Category

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.4.3 / 2011-08-10

Nice:

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.4.2 / 2011-02-18

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.4.1 / 2010-09-01

  • 2 minor enhancements:

    • Added extra error handling for ERB flay to deal with tons of bad ERB
    • Skip plugin if another version already loaded (eg local vs gem).
  • 1 bug fix:

    • Fixed all tests that were having problems on 1.9 due to unstable hashes
  • http://ruby.sadi.st/

  • http://rubyforge.org/projects/seattlerb

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.4.0 / 2009-08-14

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.3.0 / 2009-06-23

  • 5 minor enhancements:

    • Added --summary to display flay scores per file.
    • Added --verbose to display processing progress.
    • Protect against syntax errors in bad code and continue flaying.
    • Removed fuzzy matching. Never got it to feel right. Slow. Broken on 1.9
    • Renamed --verbose to --diff.
  • http://ruby.sadi.st/

  • http://rubyforge.org/projects/seattlerb

ParseTree EOL

| | Comments (4)

There seems to be some confusion and/or panic about ParseTree that I'd like to clear up:

ParseTree is dead on ruby 1.9 and there is no plan to make it work.

Because of changes to internals in 1.9, ParseTree simply can not work. I asked for hooks/options to allow us to get to the information but they never arrived.

Specifically if you're using ParseTree to access the AST of a live method/block/proc, you're SOL. If you're just using ParseTree to do static analysis, then you can switch to ruby_parser in about a minute of work and you're good to go.

Here is the plan for my projects:

  • RubyToC-1.0.0.5 = switching to ruby_parser
  • flog-2.1.0 = switching to ruby_parser
  • heckle-1.4.2 = dead, unless we can think of something soon.
  • ruby2ruby-1.2.2 = dropping block/proc support.
  • ruby_parser-2.0.2 = no clue why it has a dependency still, no worries here.
  • ZenHacks-1.0.1 = dropping block/proc support -- not that I support this.

I don't know the status of most of the projects dependent on PT or how they're going to deal with this issue. If you use one of these projects directly or indirectly and that project relies on PT for live method/block/proc, then you're probably going to be stuck on 1.8 for a while:

  • SuperCaller-1.0.0 = unsupported - can drop live method support
  • ambition-0.5.4
  • argible-0.1.1
  • integrity-0.1.9.3
  • merb-action-args-1.0.11
  • nitpick-1.0.2
  • protocol-0.8.1
  • red-4.1.7
  • reek-1.0.0 = probably doesn't need live analysis
  • roodi-1.3.5
  • ruby_diff-0.2
  • rubyjs-0.8.0
  • sake-1.0.15
  • thorero-action-args-0.9.4

There are probably other projects out there dependent on PT that I don't know about. All I've listed here are rubyforge gems that depend on PT in their gemspec.

You can check your gems using this:

gem list | egrep "(ambition|argible|integrity|merb-action-args|nitpick|protocol|red|reek|roodi|ruby_diff|rubyjs|sake|thorero-action-args)"

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.2.1 / 2009-03-16

Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad.

Changes:

1.2.0 / 2009-03-09

  • 2 major enhancements:

    • Added flay_task.rb
    • Added plugin system (any flay_(c,java,js,etc).rb files).
  • 4 minor enhancements:

    • Added expanddirsto_files and made dirs valid arguments.
    • Added flay_erb.rb plugin.
    • Added optparse option processing.
    • Refactored to make using w/in rake and other CI systems clean and easy.
  • http://ruby.sadi.st/

  • http://rubyforge.org/projects/seattlerb

flayjs... flayc...

| | Comments (2)

70 and 61 lines of code respectively...

anyone know of a java parser in ruby?

About this Archive

This page is a archive of recent entries in the flay category.

RubyInline is the previous category.

flog is the next category.

Find recent content on the main index or look in the archives to find all content.

Pages

Powered by Movable Type 4.32-en