C’s Biggest Mistake (2009)

Re:C’s Biggest Mistake (2009) by xxpor on Saturday September 12, 2020 @05:44PM (#24456091)

Isn't that what asan/ubsan is for?

Granted, it's not static analysis, but it should catch most aliasing related errors, no?

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by nsajko on Saturday September 12, 2020 @06:54PM (#24456600)

No. There has been some effort in that direction, somebody proposed a Clang "type sanitizer" patch, but it wasn't merged.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by fizixer on Saturday September 12, 2020 @06:44PM (#24456534)

I'm fully in the camp of C plus powerful analysis tools, plus a high-level language (Python or Scheme).

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by pjmlp on Sunday September 13, 2020 @02:43AM (#24458911)

Since powerful analysis tools aren't defined by ISO what they are supposed to be, there are plenty of C compilers that will never get them.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by Ar-Curunir on Saturday September 12, 2020 @06:29PM (#24456429)

only if your tests exercise that code path

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by identity0 on Saturday September 12, 2020 @09:51PM (#24457528)

You can't do compile time bounds checking, if that's what you're implying.

[ Parent | on HN ]

Re:C’s Biggest Mistake (2009) by saagarjha on Sunday September 13, 2020 @06:00AM (#24459741)

Most, but not all. They are excellent tools but not perfect by any means.

[ Parent | on HN ]