News for hackers. Stuff that matters.

A comment on How to Write Portable C Without Complicating Your Build.

Re:How to Write Portable C Without Complicating Your Build by coldtea on Friday March 31, 2017 @07:55AM (#14002844)
>The man page also documents secure_getenv(), which is a GNU extension: to be avoided in anything intended to be portable.

GCC itself is portable, so?

[ Parent | on HN ]
Re:How to Write Portable C Without Complicating Your Build by andreareina on Friday March 31, 2017 @10:27AM (#14004102)
That's like arguing that because cows are vegetarian, so is beef. Portable means that any system implementing the standard interface can use it; secure_getenv isn't part of the standard, therefore it's not portable.
[ Parent | on HN ]
Re:How to Write Portable C Without Complicating Your Build by coldtea on Friday March 31, 2017 @01:33PM (#14006069)
No, it's more like arguing that if one is OK with the (lots) of platforms GCC covers, then it shouldn't matter if some extension is GCC specific. Your program is still portable for your use cases.
[ Parent | on HN ]
Re:How to Write Portable C Without Complicating Your Build by andreareina on Friday March 31, 2017 @03:29PM (#14007300)
Not everyone uses GCC, or glibc.
[ Parent | on HN ]
Re:How to Write Portable C Without Complicating Your Build by ptman on Friday March 31, 2017 @08:04AM (#14002877) 

       secure_getenv() first appeared in glibc 2.17.
not GCC
[ Parent | on HN ]