On Tue, 7 Nov 2017, Liu Hao wrote:
On 2017/11/7 6:19, Martin Storsjö wrote:
Signed-off-by: Martin Storsjö <mar...@martin.st>
---
mingw-w64-headers/crt/stdio.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/mingw-w64-headers/crt/stdio.h b/mingw-w64-headers/crt/stdio.h
index 7365994..cea5559 100644
--- a/mingw-w64-headers/crt/stdio.h
+++ b/mingw-w64-headers/crt/stdio.h
@@ -530,11 +530,11 @@ int vsnprintf (char *__stream, size_t __n, const char
*__format, __builtin_va_li
int __cdecl asprintf(char ** __restrict__ ret,const char * __restrict__
format,...) __attribute__ ((format (__MINGW_PRINTF_FORMAT, 2, 3)))
{
__builtin_va_list ap;
- int ret;
- __builtin_va_start(ap, _Format);
- ret = vasprintf(ret, format, ap);
+ int n;
+ __builtin_va_start(ap, format);
+ n = vasprintf(ret, format, ap);
__builtin_va_end(ap);
- return ret;
+ return n;
}
#endif /*_GNU_SOURCE*/
Are there any reasons why reserved identifiers are not favored here?
Not really, it mostly comes from whichever wording was used in the place
it was copypasted from. Since these identifiers aren't visible outside of
the inline function, I don't see how it would matter. If you feel strongly
about it, there's a huge number of other inline functions with identifiers
like these.
// Martin
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
