# from chromatic
# on Friday 17 August 2007 11:28 am:
>... sort of like I've been doing for at least one and probably two
> years now with Module::Build and my custom disttest action, which I
> know I've mentioned a few times now, which leads me to wonder why
> people so conveniently forget it every time this discussion comes up.
Because
1. it doesn't play nicely with recursive tests[1]
2. it requires a custom disttest action[2]
[1] Unless you filter out t/author (and t/gui (and t/network
(and ...))) It seems to me that having a whole directory of "and also"
would more easily allow one to cherry-pick which extras to run while
leaving "t/" as the "run all of these, recursively" spot.
[2] And that wouldn't be so bad if Module::Build had a plugin
mechanism, but it doesn't. Thus, avoiding custom actions for something
where they could be avoided is nice because it reduces the (currently
necessary) copy/paste code reuse.
--Eric
--
So malloc calls a timeout and starts rummaging around the free chain,
sorting things out, and merging adjacent small free blocks into larger
blocks. This takes 3 1/2 days.
--Joel Spolsky
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
