Hi!

According to XBD, 5 ("File Format Notation"), L3071:
  ’ ’ (An empty character position.)
      Represents one or more <blank> characters
and XRAT, A.5 ("File Format Notation") agrees in L117453-117455,117456-117457:
  Note that an empty character position in format represents
  one or more <blank> characters on the output (not white space,
  which can include <newline> characters).
  The '∆' character is used when exactly one <space> is output.

So I think this is as-expected.

However, XCU, 3, cksum, L83395-83398 says:
  STDOUT
    For each file processed successfully,
    the cksum utility shall write in the following format:
    "%u %d %s\n", <checksum>, <# of octets>, <pathname>
    If no file operand was specified,
    the pathname and its leading <space> shall be omitted.

So: huh? What if you wanted to output:
  %zu\t%zu\t%s\n
A strict reading would mean that the no-operand output should be
  %zu\t%zu\t\n
(or, indeed %zu\t%zu\t %s\n -> %zu\t%zu\t\n, &c.)
but that's obviously wrong?

Is the standard's intent to require
  "%u∆%d∆%s\n"
or should the section read something like
  STDOUT
    For each file processed successfully,
    the cksum utility shall write in the following format,
    if any file operands were specified:
    "%u %d %s\n", <checksum>, <# of octets>, <pathname>
    or if no file operand was specified:
    "%u %d\n", <checksum>, <# of octets>

Line numbers from 202x/D2.1, also affects Issue 7.

(Also, if touching this, I don't really see
 how the octet count could be negative?
 So maybe the second format should be %u?
 That's minor though.)

Best,
наб

Please keep me in CC.

Attachment: signature.asc
Description: PGP signature

  • 202x/D2.1 cksum form... наб via austin-group-l at The Open Group

Reply via email to