You might consider dividing the functionality into two routines: weeder() and processor(), which you can test separately. Then have a third routine which is the one that is the API, which you can test separately. it conssist of:

sub API {
   processor(weeder( @_ ));
}
[download]