[debbugs-tracker] bug#18987: closed (the bourne shell printf-vs-\xHH portability trap)

[GNU bug Tracking System]

Your message dated Fri, 7 Nov 2014 12:12:55 -0800
with message-id <address@hidden>
and subject line Re: bug#18987: the bourne shell printf-vs-\xHH portability trap
has caused the debbugs.gnu.org bug report #18987,
regarding the bourne shell printf-vs-\xHH portability trap
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18987: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18987
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: the bourne shell printf-vs-\xHH portability trap Date: Fri, 7 Nov 2014 11:14:21 -0600

I ran grep's tests on a debian system this morning and was
surprised to see the word-multibyte test fail...
Until I realized it was because that system was configured
to use dash for /bin/sh, and this test relied on the unportable
printf '\xc3\xa1\n' to print an à (A-grave).  Using \xHH
hexadecimal constants works with bash and zsh, but that
is not portable, and dash's printf built-in emits the 9 bytes
rather than the expected three.

This isn't the first time this has happened, so I'll be writing
a syntax-check rule to help avoid another repeat.

Here's how I've fixed it:

0001-maint-move-helper-function-hex_printf-to-init.cfg.patch
Description: Binary data

0002-tests-avoid-printf-xHH-portability-trap.patch
Description: Binary data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#18987: the bourne shell printf-vs-\xHH portability trap
>
>
>
>
> Date: 
>
> Fri, 7 Nov 2014 12:12:55 -0800
>
>
>
>
> I've pushed these, and will make a new snapshot soon.
> Holler if there's anything else you think should be included.
>
>
> --- End Message ---