Displaying 4 results from an estimated 4 matches for "0123456789klmnopqrstuvwxyz".
2014 Sep 20
2
vsnprintf_s and vsnprintf
...<snip>
> vsnprintf (MSVC, MinGW):
>
> buf_size = 8; ret = -1; buffer = "01234567ijklmnopqrstuvwxyz"
> buf_size = 9; ret = -1; buffer = "012345678jklmnopqrstuvwxyz"
> buf_size = 10; ret = 10; buffer = "0123456789klmnopqrstuvwxyz"
> buf_size = 11; ret = 10; buffer = "0123456789"
> buf_size = 12; ret = 10; buffer = "0123456789"
This is actually the only one we can use.
With a check on the the return value and a line or two of extra
code, this function can made to...
2014 Sep 20
0
vsnprintf_s and vsnprintf
...;> vsnprintf (MSVC, MinGW):
>>
>> buf_size = 8; ret = -1; buffer = "01234567ijklmnopqrstuvwxyz"
>> buf_size = 9; ret = -1; buffer = "012345678jklmnopqrstuvwxyz"
>> buf_size = 10; ret = 10; buffer = "0123456789klmnopqrstuvwxyz"
>> buf_size = 11; ret = 10; buffer = "0123456789"
>> buf_size = 12; ret = 10; buffer = "0123456789"
>
> This is actually the only one we can use.
Why? We can use vsnprintf_s for MSVS, and vsnprintf for MinGW.
MSVS version o...
2014 Sep 18
3
patch for win_utf8_io.c: vsnprintf_s vs. MinGW
lvqcl wrote:
> Oops. It seems that vsnprintf_s isn't always available on MinGW platform:
> MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined.
> That's because WinXP version of msvcrt.dll doesn't contain secure functions
> like vsnprintf_s.
>
> Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf?
Ok, we need to drop
2014 Sep 19
0
vsnprintf_s and vsnprintf
...---------------------------------------
vsnprintf (MSVC, MinGW):
buf_size = 8; ret = -1; buffer = "01234567ijklmnopqrstuvwxyz"
buf_size = 9; ret = -1; buffer = "012345678jklmnopqrstuvwxyz"
buf_size = 10; ret = 10; buffer = "0123456789klmnopqrstuvwxyz"
buf_size = 11; ret = 10; buffer = "0123456789"
buf_size = 12; ret = 10; buffer = "0123456789"
---------------------------------------------------------------------------
vsnprintf (MinGW with "#define __USE_MINGW_ANSI_STDIO 1"):...