Re: [Success/exposed test failures] XEmacs 21.4.14 "Reasonable Discussion" i586-pc-win32

APA> FAIL: Assertion failed: (string= (format "%e" 100) "1.000000e+02") Stephen> Oops, oh, yeah, that too. Stephen> Funny how those Windows bugs never get fixed. There was Stephen, I looked into this a bit. These tests all fail because of a three digit exponent being printed by MS printf. Using cygwin I get two-digit exponents printed instead of three. However, reading http://www.opengroup.org/onlinepubs/007904975/functions/printf.html seems to suggest that three digit exponents are not in violation with the following excerpt: e, E The double argument shall be converted in the style "[-]d.ddde±dd", where there is one digit before the radix character (which is non-zero if the argument is non-zero) and the number of digits after it is equal to the precision; if the precision is missing, it shall be taken as 6; if the precision is zero and no '#' flag is present, no radix character shall appear. The low-order digit shall be rounded in an implementation-defined manner. The E conversion specifier shall produce a number with 'E' instead of 'e' introducing the exponent. The exponent shall always contain at least two digits. If the value is zero, the exponent shall be zero. A double argument representing an infinity or NaN shall be converted in the style of an f or F conversion specifier. Should the testcase allow three-digit as well as two-digit exponents? Is anyone aware that we rely on two-digit exponents anywhere? Adrian, having spent way too much time on this already ... Stephen> a bunch of discussion about this, but never any Stephen> resolution. Are you going to change the tests, or not? APA> Hi Stephen, I forgot all about these failures because they were APA> invisible until now. I don't run these tests interactively, but my APA> own build reports may make me do so in the future. APA> What are you suggesting for this particular problem? APA> Making these failure expected when running on native windows? APA> Convincing Microsoft to give up breaking software standards to foster APA> their monopoly? APA> Put a fix into XEmacs sources for format to work right in native APA> Windows? APA> -- APA> Adrian Aichner APA> mailto:adrian＠xemacs.org APA> http://www.xemacs.org/ -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/