4 ms·
The reason it's not calleld init_time_after_boot - well, first of all Microsoft coding standards call for CamelCase. But secondly, there are several "times", a
by sounddust 18y ago
The reason it's not calleld init_time_after_boot - well, first of all Microsoft coding standards call for CamelCase. But secondly, there are several "times", and there are several ways to "initialize" something, and there are several meanings to "boot."
You're either going to have a naming conflict, or you're going to have a bunch of idiots who wanted to initialize a different clock, who start posting to forums saying "i don't understand???! i called init_time waht's wrong???"
Sure, they could call it
SendTheIOCTLCommandToInitializeTheRealTimeClockForTheOEMAbstractionLayer
but sometimes the names of functions are going to be ugly.