Re: init.sh and C tests

2010-05-23 Thread Bruno Haible
Hi Jim, > Currently I've been creating a tiny script like this for each > program I want to wrap, git-adding it, and listing it in Files:, too. > Taking test-areadlink-with-size as an example, > > #!/bin/sh > . "${srcdir=.}/init.sh"; path_prepend_ . > test-areadlink-with-size > Ex

Re: init.sh and C tests

2010-05-23 Thread Jim Meyering
Bruno Haible wrote: >> Not having to worry about cleaning up temporary files >> and not having to choose "parallel-safe" names for them >> leads to much cleaner tests. >> Not having to add signal handlers in every single one >> avoids duplication and would make them robust by default. >> >> IMHO, a

init.sh and C tests

2010-05-23 Thread Bruno Haible
Hi Jim, > Not having to worry about cleaning up temporary files > and not having to choose "parallel-safe" names for them > leads to much cleaner tests. > Not having to add signal handlers in every single one > avoids duplication and would make them robust by default. > > IMHO, all new tests shou