coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Whats the reason to suppress short unicode characters in printf?


From: Eric Blake
Subject: Re: Whats the reason to suppress short unicode characters in printf?
Date: Tue, 5 Apr 2016 08:02:14 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1

On 04/04/2016 10:01 PM, Jim Meyering wrote:
> On Mon, Apr 4, 2016 at 7:43 PM, Mike Frysinger <address@hidden> wrote:
>> the code as written has existed since it was first committed in Mar 2000:
>> http://git.savannah.gnu.org/cgit/coreutils.git/commit/?h=29d3ba4a7b42ed1b40b963b6047f2412ea4843b1
>> although the Author says Jim, the ChangeLog file says Bruno Haible.
>>
>> that predates the merge of file/text/shell utils into coreutils (2003),
>> and printf was part of the shellutils project.  unfortunately the history
>> is pretty spotty that far back ... here's its mailing list archive:
>>         https://lists.gnu.org/archive/html/bug-sh-utils/
>>
>> so i guess really you'd have to ask Bruno and/or Jim.  my guess is that
>> it comes from the C standard:
>>         http://c0x.coding-guidelines.com/6.4.3.html
>> and you might find this interesting:
>>         http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2170.html
>>         http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3881.pdf
> 
> I confirm it was a patch by Bruno Haible.
> I have a copy of a message from him with the following changes
> that appears to have been sent only to Markus Kuhn and me.
> As he explained, these changes were motivated by the then-recent
> approval of ISO C99. Here are the ChangeLog entries:

That said, it may be time to consider teaching coreutils to accept ALL
\uXXXX escapes, rather than just the ones required by C99, as an
extension for ease of use.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]