"%#s"?
Karl Heuer
karl at haddock.ISC.COM
Sat Jun 18 02:23:21 AEST 1988
In article <324 at proxftl.UUCP> bill at proxftl.UUCP (T. William Wells) writes:
>You do not want to use short octal escape sequences [for %#c or %#s encoding]
>because the string "\a0" could be output as "\70" which is ambiguous. For
>similar reasons, if X3J11 leaves in the unlimited length for "\x", those
>can't be used.
Which means that there are some strings% that can't be output at all, except
by writing every single character -- including the printable ones -- in hex.
(The string-literal-pasting kludge doesn't help here.)
I'll make one more effort in the third public review to convince X3J11 that my
\c terminator is useful. See comp.std.c for a discussion thereof.
Karl W. Z. Heuer (ima!haddock!karl or karl at haddock.isc.com), The Walking Lint
% Consider a machine with 12-bit bytes, printable chars being 0x400-0x4ff.
More information about the Comp.lang.c
mailing list