Eric Blake wrote: > > + * tests/test-exclude1.sh: Handle Windows EOL. > > Rather than adding a tr process, would it instead make sense to make > test-exclude.c use the binary-io module to ensure binary output, so that > no \r are generated in the first place?
The technique of piping through 'tr' is applicable, regardless whether you want to check the output of your package's main program (such as 'm4', 'xgettext', 'find', 'ls', etc.) or whether a specially test-*.c program is being used. The technique of using the binary-io module works only in the latter case. I prefer the technique that is more universally applicable. Bruno
