On 09/03/19 05:52, Bruno Haible wrote: > Hi Pádraig, > >>>> In regard to options for enabling various behaviors for wc(1), >>>> I'm thinking we might keep the strict POSIX isspace() behavior >>>> with LC_CTYPE=C and/or POSIXLY_CORRECT=1, and use iswnbspace() >>>> by default > > Since you plan to add a --words=... option in the future (as suggested > by Paul or me), it would make sense to add this option now, instead > of testing POSIXLY_CORRECT. If you introduce POSIXLY_CORRECT dependent > behaviour now (and need to keep it for backward-compatibility), you'll > have a hard to understand interface: What will the following do? > > env POSIXLY_CORRECT=1 wc --words=unicode > wc --words=unicode
Well until we actually support more contextual unicode word separation operation, the --words option parameter would be a bit redundant. Generally no-one would need to use POSIXLY_CORRECT directly with wc, rather setting it globally on a system or script to minimize changes. In the above example --words=unicode would be an explicit option to operate in extension to POSIX, and so POSIXLY_CORRECT would be ignored there. cheers, Pádraig
