3 ms·

While I commend this effort I should say that seriously, just write C++ if possible. No matter what you do memory management is going to be your biggest enemy (

While I commend this effort I should say that seriously, just write C++ if possible. No matter what you do memory management is going to be your biggest enemy (I’m ignoring the aesthetic aspects like macros, function pointers, type safety, etc). Without RAII it’s just not worth it. Just choose the simpler portions of C++ and keep safe.

oso2k 4y ago
You can do RAII in C. You still have to define a dtor function. https://en.wikipedia.org/wiki/Resource_acquisition_is_initialization#Compiler_%22cleanup%22_extensions https://en.wikipedia.org/wiki/Resource_acquisition_is_initia...
- anthomtb 4y ago
  Is "dtor" shorthand for destructor?
  - jacquesm 4y ago
    Yes, just like ctor is constructor.
  - oso2k 4y ago
    Yes! You got it.
- posharma 4y ago
  I am aware of this "non-standard" extension. My comment was w.r.t sticking to the standard.
matiasfernandez 4y ago
I never have trouble with memory management in C by sticking to "grouped element architectures" with explicit lifetimes such as arenas, scratch allocators, dynamic pools, etc. RAII is mostly for "single element architectures" which IMO are not a good way to organize code because they tend to amount to thousands of unnecessary memory operations.
yakkityyak 4y ago
Yeah, I feel like “C in a C++ Compiler” is a respectable decision for reasons similar to what you describe.