Jeff King <peff@xxxxxxxx> writes: > [2] For the most part, actually, I think the status quo is using > test_cmp, and most of the uses of "test" are old. Using test_cmp is > more verbose, but it does have the advantage of checking the exit > code of the sub-programs (and also its output is much saner for > multi-line comparisons, but that isn't relevant to Paul's patches). > > I'd be in favor of helpers that made it shorter to use test_cmp. > E.g.: > > # "actual" contains "foo\n"; we save one line of "echo" > git foo >actual && > test_cmp_str foo actual > > # same, but take multiline input on stdin. Saves one line of "cat" > git foo >actual && > test_cmp_str - actual <<-\EOF > foo > EOF > > # similar, but it runs the command for us and compares its > # stdout, saving another line. Note that we take stdout as-is, > # so you get no opportunity to post-process it (but you > # can still do it the "long" way as above if you need to). > test_cmp_cmd foo git foo > > # same, with stdin; obviously this doesn't work if you need to > # send something over stdin to the command, but again, you can > # fallback to the old way. > test_cmp_cmd - git foo <<-\EOF > foo > EOF > > These also go in the direction of "verbose", by providing generic > solutions rather than specific ones. So by the argument you made > above, this is a bad thing. I do not agree with that. Perhaps "unconstained" was an unfit phrase. "test_cmp_cmd expected-string git foo" may be "test $a = $b" inside, but its debug error message could be made to say "output from 'git foo' is different from 'expected-string'", which is a very good thing. Contrast that with: verbose test "$(git foo)" = "expected-string" which would not give you that information (and you'd need to do the "-x" thing to find out where the string that is different from the expected string came from). Ultimately that is because 'test' that an individual test script writes in it does not constrain what is on each side of comparison (for that matter, it does not even constrain that what is tested is comparison between two things), which makes it very hard to give useful diagnoses. 'test' itself operates at too low a level, and wrapping it with 'verbose' does not recover the information already lost when invoking 'test'. So, I suspect we want more or less the same thing. We agree that we need shorter, easier to use, and less error prone idioms, like test_cmp (comparing two files and show the differences as diagnosis), test_cmp_rev (comparing two extended SHA-1 expressions as object names), and test_line_count (checking the number of lines in a file). I just do not think "verbose" that can apply to any command will help us move in that direction very much, and I find that "verbose" applied to something overly versatile like "test" is a prime example that it does not help us much. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html