CxxTest/cxxtest — comment on commit f50d7d67a41ba76c6c2db2e41e1619e0b99beae6
File:  line 0
By whart222:

Unfortunately, this change broke a lot of tests. The asString()
command is used to generate the output that is used in many of the
examples.

Your motivation for this change remains unclear, and hence I am
struggling to suggest an alternative. Why do we need to make these
characters visible? When?

--Bill

On Sat, Mar 3, 2012 at 7:17 PM, Allan Odgaard

wrote:
> The `\t`, `\r`, and `\n` characters are all “ invisible” so if e.g. testing a function to harmonize line endings or indentation, the test output without using the escaped form will not be helpful.
>
> By doing this, escaping backslash naturally follows to keep it from being ambiguous.
>
> Escaping of the double-quote was added for aesthetic reasons (now that escapes were introduced). The entire string is double-quoted in the error output so it seemed wrong to have non-escaped double-quotes inside the string.
>
> As for breaking tests, I assume it is breaking tests about how `asString` should format a string? I.e. the patch should have updated the test as well for the new output.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/CxxTest/cxxtest/commit/f50d7d67a41ba76c6c2db2e41e1619e0b99beae6#commitcomment-1039589