TIL: this is something... you can dopic.twitter.com/YVkCdJZKPP
-
@fioraaeterna Also, failing to check the return value of malloc() is my pet peeve.
@dev_console @FioraAeterna well.. *most* implementations overcommit. i.e. unless you run out of address space malloc() never returns NULL.
-
-
@oe1cxw@fioraaeterna And overcommit is a terrible thing for robustness — see http://www.etalabs.net/overcommit.html (“X considered harmful” style aside) -
@dev_console@FioraAeterna sure. I did not mean to say it's a wonderful idea. Just that checking malloc() retval on 64 bit OS is pointless.. - Show replies
New conversation -
-
-
@oe1cxw@fioraaeterna I don’t think it’s fair to punish implementations that are doing The Right Thing for robustness from that perspective. -
@dev_console@FioraAeterna Out of curiosity: What would you do if malloc() returns NULL on POSIX OS? Can't use stdio reliable then I guess..
End of conversation
New conversation -
-
-
@oe1cxw@dev_console@FioraAeterna On any normal 32-bit system running out of address space is much more likely than exhausting ram+swap.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.