> I think the data will support the idea that a directory structure based
on OS/CPU is probably not the way to start.
>
Quite possibly. The proposed file could suffer from the same combinatorial
explosion, if not properly structured. Does anyone have a good idea of the
most economical structure for the exceptions? I do like the idea of
embedding conditions in data rather than code structures, though.
> Instead, one might consider generating that list of exclusions based on
the actual results of running Configure.pl. The program that generated
that skip list might consist of lines like
>
> print "t/op/64bit.t" unless $PConfig{intvalsize} == 8;
>
Or "touch x.t if some_state". As the problems of maintaining lists of
filenames have already been solved, it seems a shame not to use well-known
tools like ls, rm, diff, and their friends.
--
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com
