Banned C standard library functions in Git source code

Re:Banned C standard library functions in Git source code by zsrxx on Sunday August 25, 2019 @10:25AM (#20793125)

Wanting code to compile on something other than gcc is not "caring too much", it's being responsible

[ Parent | on HN ]

Re:Banned C standard library functions in Git source code by adrianN on Sunday August 25, 2019 @10:43AM (#20793260)

For this particular case it wouldn't be a big deal. The code is still valid C, it's just that GCC makes sure that you don't use the poisoned values.

[ Parent | on HN ]

Re:Banned C standard library functions in Git source code by The_rationalist on Sunday August 25, 2019 @10:29AM (#20793161)

Responsible? What an hyperbolic statement. Could you enlighten me on what would be the significant negative consequences? I hope that your mental equation take into account the missed usefulness of GCC only attributes, flags and extensions by being clang compatible.

[ Parent | on HN ]

Re:Banned C standard library functions in Git source code by zsrxx on Sunday August 25, 2019 @10:33AM (#20793192)

I don't know what to tell you. Do you think all compilers should implement all GCC proprietary extensions, basically creating a parallel C standard?

And that's not saying that GCC extensions are not useful, but they should not be considered the norm

[ Parent | on HN ]

Re:Banned C standard library functions in Git source code by klez on Sunday August 25, 2019 @10:36AM (#20793213)

Agreed. But I wonder if we already have a sort of parallel C standard already with POSIX (of course the parts about C, not about OS facilities).

[ Parent | on HN ]