Sjmarf@sh.itjust.works to Programming Horror@programming.dev · 29 days agomallocPlusAIsh.itjust.worksimagemessage-square23fedilinkarrow-up1168arrow-down10
arrow-up1168arrow-down1imagemallocPlusAIsh.itjust.worksSjmarf@sh.itjust.works to Programming Horror@programming.dev · 29 days agomessage-square23fedilink
minus-squarezaphod@sopuli.xyzlinkfedilinkarrow-up11·29 days agoYou don’t need to cast the return value from malloc.
minus-squareaddie@feddit.uklinkfedilinkarrow-up7·29 days agoTrue. Although given how easy it is to cast void pointers to the wrong damn thing, it would be nice if you did, makes refactoring much easier. Makes me appreciate std::any all the more.
minus-squareembed_me@programming.devlinkfedilinkarrow-up2·edit-227 days agoVoid pointer should be avoided anyways. Even I find them rare and I mostly work in embedded RTOS
minus-squarevrighter@discuss.tchncs.delinkfedilinkarrow-up1·27 days agothat is besides the point. You can still call malloc, it will still return void*, and it would still reqoire casting in c++
You don’t need to cast the return value from malloc.
True. Although given how easy it is to cast void pointers to the wrong damn thing, it would be nice if you did, makes refactoring much easier. Makes me appreciate
std::anyall the more.Void pointer should be avoided anyways. Even I find them rare and I mostly work in embedded RTOS
you do in c++, no?
In c++ you should use
new.that is besides the point. You can still call malloc, it will still return void*, and it would still reqoire casting in c++