-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Joseph A. Wiencko, Jr. on 9/13/2006 9:57 PM: > > Another way of saying it, in a question format, is "Is there ANY > collating sequence in which the example I posed makes sense for the > behavior of comm? If so, please name one." > > This logical error, regardless of collating sequence, is why it appears > to be a bug.
As Andreas explained, if your inputs are not already sorted according to the current locale, then using comm on those files does not have to produce reliable output. Garbage in, garbage out. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCSTz84KuGfSFAYARAu6sAKCz4mQKY5quMsqLOstohWDPpVDA5ACfeK9Z D2OtnxahOrlSCf+iTN+7hTo= =BWHr -----END PGP SIGNATURE----- _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
