[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %.1s format with vasnprintf reads more than one byte from argument
|
From: |
Bruno Haible |
|
Subject: |
Re: %.1s format with vasnprintf reads more than one byte from argument |
|
Date: |
Tue, 24 Feb 2009 12:36:18 +0100 |
|
User-agent: |
KMail/1.9.9 |
Ben Pfaff wrote:
> it only did it after I had done some manual editing of Makefiles,
> etc. produced by configure, and much source hacking.
Somhoew this must have led to a situation where HAVE_SNPRINTF = 0.
> So to make sure that it could really happen in a simple test
> case, I forced !USE_SNPRINTF by editing vasnprintf.c manually.
Well done. I did the same.
> the comments include a number of usages of
> the ligature for "fi", in the word "specified", instead of
> separate letters "f" and "i".
Oops. Fixed. But at least the spaces were real spaces, not U+00A0s :-)
Bruno
- %.1s format with vasnprintf reads more than one byte from argument, Ben Pfaff, 2009/02/23
- Re: %.1s format with vasnprintf reads more than one byte from argument, Bruno Haible, 2009/02/23
- Re: %.1s format with vasnprintf reads more than one byte from argument, Ben Pfaff, 2009/02/23
- Re: %.1s format with vasnprintf reads more than one byte from argument,
Bruno Haible <=
- Re: %.1s format with vasnprintf reads more than one byte from argument, Eric Blake, 2009/02/25
- Re: %.1s format with vasnprintf reads more than one byte from argument, Eric Blake, 2009/02/26
- Re: %.1s format with vasnprintf reads more than one byte from argument, Bruno Haible, 2009/02/26
- Re: %.1s format with vasnprintf reads more than one byte from argument, Eric Blake, 2009/02/26
- Re: %.1s format with vasnprintf reads more than one byte from argument, Bruno Haible, 2009/02/27
- Re: %.1s format with vasnprintf reads more than one byte from argument, Eric Blake, 2009/02/27