News for hackers. Stuff that matters.
Re:The Safe C Library (2009) by danieltillett on Thursday April 13, 2017 @08:38AM (#14106261)
This is so true. It seems like most of the arguments against C are made in isolation of the ecosystem that has been built around C. At this point we should be helping new programmer learn how to work with C with all the safely equipment we now have.
Re:The Safe C Library (2009) by pjmlp on Thursday April 13, 2017 @09:20AM (#14106576)
Because only around 1% of all C developers care to use such band aids.
Re:The Safe C Library (2009) by Nokinside on Thursday April 13, 2017 @09:37AM (#14106718)
They are not band aids.

Analysis tools for C exceed anything you can have in Rust or Go compiler in scope and features.

Re:The Safe C Library (2009) by pjmlp on Saturday April 15, 2017 @08:23AM (#14120449)
Something that is optional doesn't exceed what are standard safety features in programming languages since Algol and its derived languages exist.

Having external tools to track out of bonds errors, use after free, double free, free bad pointers, implicit conversions and UB, errors that don't happen in another languages is band aid.

Other languages just don't need them thanks to being designed with safety first.

Re:The Safe C Library (2009) by danieltillett on Saturday April 15, 2017 @06:58PM (#14123310)
I write in C (mostly) and very few of my bugs are the typical errors C is famous for - 99.9% are logic bugs that can occur in any language. I have lots of great tools to catch the C type bugs - I wish I had a tool to catch my logic bugs. Tests can only find the bugs where the code doesn't do what I expect, not where what I expect is wrong.
Re:The Safe C Library (2009) by pjmlp on Sunday April 16, 2017 @01:39AM (#14124524)
Which tells me that you work alone without other devs of various skillsets messing around your beautiful C code.
Re:The Safe C Library (2009) by danieltillett on Sunday April 16, 2017 @03:24AM (#14124791)
Well I wouldn't call my C code beautiful, but no I don't work alone. I do only work with devs better than me :)
Re:The Safe C Library (2009) by Nokinside on Wednesday April 19, 2017 @11:53AM (#14148625)
>Other languages just don't need them thanks to being d esigned with safety first.

Other languages are not used for writing safety critical code. Language features are not even close being enough for that.

Re:The Safe C Library (2009) by pjmlp on Thursday April 20, 2017 @11:16AM (#14157422)
Ada and SPARK are such languages, better improve your knowledge.
Re:The Safe C Library (2009) by Nokinside on Friday April 21, 2017 @01:16PM (#14167411)
I specially mentioned Ada with C/C++ in my first post that started the tread.

No need to defensively boast if you realize that you are wrong.

Re:The Safe C Library (2009) by pjmlp on Friday April 21, 2017 @07:01PM (#14170123)
I don't need to be defensive in any way.

The band-aids called MISRA-C, Frama-C, High Integrity C++ and DOD certifications are a mechanism to force Ada safe like semantics in C and C++, while paying lower salaries, instead of hiring Ada devs.

F-35 proves how good they work out in large scale projects.

Re:The Safe C Library (2009) by danieltillett on Thursday April 13, 2017 @07:11PM (#14111558)
Exactly. The real problem is many C developers are unaware of these tools. Rather than just saying use programming language x, we should be helping people use C with the right tools.
Re:The Safe C Library (2009) by pjmlp on Saturday April 15, 2017 @08:25AM (#14120456)
Not at all.

These tools exist since 1979, it hasn't changed anything.

C doesn't deserve a place on any security conscious developer toolbox.