Re:Practical Guide to Bare Metal C++
by jerf on Friday June 02, 2017 @02:56PM
(#14472448)
"Would you also abort on other resource allocation errors, such as opening a socket, or creating a process wide mutex or whatever?"
You seem to believe this is not a common choice? I've seen plenty of programs crash on being unable to open a socket/file.
I'm not saying this is a good thing, just that your rhetorical implication that it is unusual seems misplaced.
And it's not always even that bad. It is true that something can be done, yes, but that something often requires massive fundamental rearchitecting of the core paradigm of the system or something. In most modern languages it isn't that easy to try to deal with resources problems. Erlang could probably do it, and... uhh... I'm already running out of possibilities here.
You seem to believe this is not a common choice? I've seen plenty of programs crash on being unable to open a socket/file.
I'm not saying this is a good thing, just that your rhetorical implication that it is unusual seems misplaced.
And it's not always even that bad. It is true that something can be done, yes, but that something often requires massive fundamental rearchitecting of the core paradigm of the system or something. In most modern languages it isn't that easy to try to deal with resources problems. Erlang could probably do it, and... uhh... I'm already running out of possibilities here.