Ramon Santamaria asked why one compiler appeared to produce different behavior than others. The underlying technical reason is much more interesting than a simple answer of "undefined behavior".
If you wonder about those magical bytes in between allocations, there is a hint.
---
Think about pairing function to calloc/malloc to release the memory.
How would you implement it?
It's signature is `free(void *ptr)`
Yes, very good hint :) Of course this is only specifically about the magic bytes, not the zeroes, just to make sure everyone is on the same page.
- Casey
Hi Casey,
I haven't seen any updates about the second video ... if it's still baking, no problems but just don't want to miss it.
PS: I'm more of a lurker but just want to say thank you for your efforts in this area. You renewed my interest in programming.
Thanks.
You didn't miss it! I was actually away this week, so I am only just back to work on it now :)
If you wonder about those magical bytes in between allocations, there is a hint.
---
Think about pairing function to calloc/malloc to release the memory.
---
How would you implement it?
---
It's signature is `free(void *ptr)`
Yes, very good hint :) Of course this is only specifically about the magic bytes, not the zeroes, just to make sure everyone is on the same page.
- Casey
Hi Casey,
I haven't seen any updates about the second video ... if it's still baking, no problems but just don't want to miss it.
PS: I'm more of a lurker but just want to say thank you for your efforts in this area. You renewed my interest in programming.
Thanks.
You didn't miss it! I was actually away this week, so I am only just back to work on it now :)
- Casey