NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Still not convinced :-) (Score:1)
The efficiency argument doesn't persuade me.
If you need ordering for the production code then it's needed by the problem domain and it obviously makes sense.
If ordering is not needed by the production code and just makes the test more convenient to write then it smells to me. You're unnecessarily exposing implementation details to the test suite.
You're also swapping slower tests for slower pro
Re:Still not convinced :-) (Score:2)
I think I should have been clearer about the "apply logic as early as possible" rule. I'm not advovating applying unecessary logic. I'm advocating applying the logic as early as is reasonable. If you need your database records sorted, sort them in the database, if possible. This discussion, to be quite frank, came from me working on some code which returns records in database order and is sorted after it's fetched, but this led to places in the code where it should have been sorted, but wasn't. I was v
Re:Still not convinced :-) (Score:1)
What chromatic said :-) Things like eq_set from Test::More or cmp_set and cmp_bag from Test::Deep.
Reply to This
Parent