Daniel Bittman

@dbittman@discuss.systems
297 Followers
117 Following
1.2K Posts

PhD candidate at UCSC working on Twizzler (twizzler.io). If it ain't broke, let's try to break it!

Black lives matter. Trans rights are human rights.

Websitedbittman.com
Pronounshe/him
Altdbittman@types.pl
Looking forward to sharing wisdom tomorrow
The sleepy kitties
They're so tiny!
Looking forward to my talk at hpts on Monday!
hey if you're having a stressful day, pawse for a moment, here
Love to think about unix security models
×
Looking forward to sharing wisdom tomorrow
@dbittman I would like to subscribe to your newsletter
@dbittman malloc never hurt anyone...not the stack or the heap.
@leean00 mine does 😈

@dbittman Oh, your malloc ;) heheh

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

@dbittman the perils of non-quantitative specifications in systems programming!
@dbittman friends don’t let friends memcpy()

@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.

@dbittman sorta just picturing dereferencing whatever