Daniel BittmanMay 21
Looking forward to sharing wisdom tomorrow
Show threadLoaferMay 21
@dbittman malloc never hurt anyone...not the stack or the heap.
Show threadDaniel BittmanMay 21
@leean00 mine does 😈
Show threadLoafer

@dbittman Oh, your malloc ;) heheh

Sounds a little more like Mina Malloc...if you get my *ref

May 21 at 2:27amWeb
×
Daniel BittmanMay 21
Looking forward to sharing wisdom tomorrow
Show threadRob RicciMay 21
@dbittman I would like to subscribe to your newsletter
Show threadDevMay 21
@dbittman ENDORSE
Show threadLoaferMay 21
@dbittman malloc never hurt anyone...not the stack or the heap.
Show threadDaniel BittmanMay 21
@leean00 mine does 😈
Show threadLoaferMay 21

@dbittman Oh, your malloc ;) heheh

Sounds a little more like Mina Malloc...if you get my *ref

Show threadRyan DoengesMay 21
@dbittman the perils of non-quantitative specifications in systems programming!
Show threadFred MoyerMay 21
@dbittman friends don’t let friends memcpy()
Show threadocratatoMay 21

@dbittman Not a new idea.

NASA has a set of coding standards (for stuff that needs to be highly reliable) that avoids dynamic allocation.

In the early days of computing your program would be given a chunk of memory and it was entirely up to your program what was code and what was data. You could overwrite code with other code, or data, as you pleased. Many hours were spent planning how the program would shuffle stuff about.

I hope never to have to do either.

Show threadRob SisonMay 21
@dbittman sorta just picturing dereferencing whatever