catch all the possible reallocs that could return a NULLto later be…#193
catch all the possible reallocs that could return a NULLto later be…#193
Conversation
|
@sezero any thoughts or comments? |
|
|
I'm heading off to bed, feel free to commit into this pull request if you see something that should be fixed. I'll catch up with this tomorrow. Thanks for reviewing. update: Back... |
|
cb85b69: Made it to compile c89-only compilers. I still don't like this. We are not really handling errors. Not really. This needs more more work, and I believe it isn't that urgent. |
|
No, it isn't urgent. If a library can't reallocate memory, then we're screwed anyway. A null dereference will cause a seg fault (or something similar in windows), which is worse than having a library just 'exit'. So I can understand 'logging' the issue, but we still need to warn the application about the issue so that it can be aware of the issue. |
|
This PR is ancient.. not sure if it's still worth it or will need re-work later? Otherwise I close |
As you wish. |
7801a34 to
6721ab9
Compare
|
I rebased this myself (and even did a minor correction.) It compiles but
If you are interested in this patch, those issues need to be resolved. |
…dereferrenced
Try catching issues raised here:
#192 (comment)