How to dismantle a compiler bomb

Re:How to dismantle a compiler bomb by bArray on Friday March 09, 2018 @09:31PM (#16556775)

It's because you can initialize the array with particular values, like: `type a[3] = { 1 , 2, 3 };`.

But I agree that it would make sense to fill the array (or have an easier method to do that), it may just be an argument of speed. I think OSes generally hand over uninitialized memory zero'ed out to prevent reading of memory from previous programs - so it's a case of allocating the memory space and then continuing, as opposed to setting values for each position.

[ Parent | on HN ]

Re:How to dismantle a compiler bomb by jotux on Saturday March 10, 2018 @02:44AM (#16557594)

Until now, I always thought this:

    int array[5] = {X};

Could be be used to set all values of the array to X, but have never used it for anything other than 0. That's somewhat surprising behavior.

[ Parent | on HN ]