On Feb 12, Jay McCarthy wrote:
> Some ideas to solve this:
>
> 1. Do not notify on changes forever
>
> 2. Change the files to not change (or make a cmdline option that
> turns it off)
>
> 3. Write wrapper programs just for DrDr in tests/drdr that filter
> the changing text
>
> 4. Add an SVN property to control what DrDr ignores
>
> --
>
> I don't like 1 because I don't think 30-ish files should prevent a
> useful piece of data from being used for the thousands of other
> files.
>
> 2 isn't satisfying because the changing information may be useful
> for humans and some changing may be necessary (printing of random
> seeds and random programs to debug when something breaks.)
>
> I like 3 because it is flexible, but it makes DrDr a deeper part of
> the tree than it already has become.
>
> Eli likes 4 because it keeps DrDr more independent. I don't like 4
> because I want to "keep everything in the language". I can see the
> property becoming equal to 3 except through an awkward interface.
#4 can be just as in-the-language as #3, it's only the extra file that
is not needed, which is particularly fitting for a single-line
configuration-like file.
* If I need to (a) write another piece of program, (b) set props on it
and on the original, (c) remember that this extra file is unrelated
to my own tests, then I likely will not do it.
* OTOH, if all I need to do is to set a property on the file with a
single expression then things for me are much easier: drdr will (a)
use that as a filter for the file the proerty is on, (b) will use
that expression in the right language, (c) I don't need to deal with
wrapper files in my test directory.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
