This is about a bad language that force GOOD developers to figth against it.
"Always use memset onto struct variable before usage, because by default it's filled with garbage."
See? The language PUT GARBAGE on your code. Good or bad developer, not matter.
Now, a more experienced developer will remember that it need to correct the problems the language force on ALL the users.
Not all the blame is in the people. Somethings, the tools are at fault, too..
It didn't put it there. It just allocated some memory. Not more, not less. If you, for example, malloc a large chunk of memory but don't intend to use it sequentially or not right away, you can save time by not memset'ing it to zero, which would be pointless. C gives you the liberty to defer the initialization, but if you're careless, you'll shoot yourself in the foot. It's very much like having a car with manual vs. automatic transmission. More power = more responsibility. If you need power, you have to accept some compromises, and in this case, the compromise is that you need to mind what's in your memory all the time.
And in relation to this post, the behaviour is not the same across compilers/archs? Thats nuts.
Is crazy the amount of punishment a developer accept, and when the fail is elsewhere, it blame itself ;)
struct Foo foo;
foo_init(&foo, bar, baz, quux);
If you do need to zero-initialize foo, you can do that easily:
struct Foo foo = { 0 };Sorry to ask this. I have lived outside the C madness this 18 years (pascal and other more saner stuff..), except now using obj-c/js and is crazy the amount of small weird stuff it have..
This make my ask: From where it get the garbage?
Clear the data is costly in the long run? I have read yesterday about data oriented design and it make me understand that now is costly to access memory.