News for hackers. Stuff that matters.
Re:45 years since its creation. The C language still very po... by pjmlp on Wednesday May 25, 2016 @01:46AM (#11767881)
Also a pragmatist, as although I tend to bash on C on every occasion and would rather not use it, if a customer does require it, I will use it.

For me a kind of escape path from C, back when I was into Turbo Pascal, was to move to Turbo C++. I only got to use Turbo C around one year before getting to learn about this new cool language called C++.

It allowed me to keep some of the Turbo Pascal safety around.

What are your approaches when using plain C, coming from "so I do have a fondness for the Pascal family of languages. I also love type-safety" ?

My solutions were:

- Use translation units as TP units, only exposing functions and struct accessors (macros if function calls were too expensive)

- Always make use of debug functions to validate pointers in debug builds (e.g. _malloc_dbg, _CrtIsValidPointer on Windows)

- make use of const as much as possible

- write my own wrappers around strncpy and friends

- compile warnings as errors

- if given the option, just use C++ instead and prefer library types to inherited C ones (string, array, references, RAII).

There are no comments on this comment yet.