6 minutes ago, John Clements wrote:
>
> In my experience, the one compelling reason not to include unit
> tests in the same module is to trim the 'require' chain for modules
> that are included in the DrRacket startup.
Yeah -- but much more than just drracket. (And that's in addition to
the discussion on dependencies.) Consider some tests that start some
subprocess that is supposed to help testing -- you wouldn't want that
on normal runs.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/users
