News for hackers. Stuff that matters.

A comment on Glibc getaddrinfo stack-based buffer overflow. Parent comment

Re:Glibc getaddrinfo stack-based buffer overflow by pjmlp on Tuesday February 16, 2016 @03:54PM (#11113047)
As I mentioned, C is legacy for Microsoft.

The way forward for C on Windows from Microsoft own SDK is to use the clang frontend + Visual C++ backend, or another C compiler from someone else.

[ Parent | on HN ]
Re:Glibc getaddrinfo stack-based buffer overflow by autoreleasepool on Tuesday February 16, 2016 @04:04PM (#11113114)
I definitely support that initiative. The more C++ programmers we can get to stop writing C the better.
[ Parent | on HN ]
Re:Glibc getaddrinfo stack-based buffer overflow by pjmlp on Tuesday February 16, 2016 @05:12PM (#11113533)
Me too.

Yes, C++ is as unsafe as C, given its copy-paste compatibility, but at least it provides the tools to program safely (if one chooses to) and the C++ community cares much more about safety than the C one.

[ Parent | on HN ]