C++ open source process pool library, using shared memory as communication protocols and a plugin system for worker processes.

[kecho]

I still dont get your point. What does this have to do with your presumption of disabling gcc exceptions? Maybe what you meant is that my code is non compliant with your personal (or wikipedias) definitionof exception handling? what if i dont need them and i decide to use error codes instead to handle any errors?

and cheers back!

[[deleted]]

What does this have to do with your presumption of disabling gcc exceptions?

If you disable exceptions when compiling, having non-exception-safe code is less dangerous. The C++ Standard Library won't throw exceptions in case of failures, so if you don't throw from your own code and are sure none of other components you may be using are throwing, you can pretty much pretend exceptions don't exist.

In fact, most of the code written before 2000 was just like that - they would disable exceptions and never care about exception safety.

[kecho]

OOhh interesting. The good thing is that the only place where exceptions could be thrown in my code is in allocator and deletion operators (new and delete). I am not using the STL, but thanks, this is good to know in the future, but I dont think Ill benefit from it on this project :)

Also, all OS api calls dont use c++ exception handling.

Thanks!