This is a feature suggestion (didn't find where to set the issue type).
Currenty (0.6.0), when the user sets a higher number of required matches than 2
and RubyRipper fails to find enough matching chunks, the version from the first
try is used (if I'm reading the sources correctly) even if some later tries
delivered versions with more matches.
In effect, this means that setting required matches to e.g. 3 can provide a
worse result than setting required matches to e.g. 2, since those chunks that
were matched two times will not be used in places where three matches were not
found.
Original issue reported on code.google.com by cere...@gmail.com on 4 Mar 2011 at 7:39
Original issue reported on code.google.com by
cere...@gmail.com
on 4 Mar 2011 at 7:39