Generate raw WAV output by hooking malloc and read

Re:Generate raw WAV output by hooking malloc and read by fredophile on Tuesday July 29, 2014 @10:48AM (#8102473)

It's always the same for your compiler. Using sizeof improves the portability of the code. Because sizeof is calculated at compile time it doesn't make the code any less efficient.

We often think about pointers as being 4 bytes but that isn't necessarily the case. How would a 32 bit pointer map to the addressable memory of 64 bit hardware?

[ Parent | on HN ]

Re:Generate raw WAV output by hooking malloc and read by reubenmorais on Tuesday July 29, 2014 @03:55PM (#8104588)

I think his point is more about clamping the value than about using sizeof. It indicates the author expected that value to vary, but it doesn't.

[ Parent | on HN ]

Re:Generate raw WAV output by hooking malloc and read by fredophile on Tuesday July 29, 2014 @08:11PM (#8105722)

Depending on your application I can see where you might still want to clamp the result. However, I think you're right in this case since the clamped range doesn't make much sense here.

[ Parent | on HN ]