MILLISEC_PER_SEC is never needed
-
Hence the elipsis - I can't put a dot over a three reliably (there's no HTML overstrike-and-superscript tag that I know of)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
\_\_0.0833
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
Well, obviously; they're measured in barleycorns[^]. Everybody knows that! :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
\_\_0.0833
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
Or the simpler option: 0.0833 (Assuming the hamsters don't eat the style.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
protects against people who see "Milli-" and think "1,000,000"
-
Or the simpler option: 0.0833 (Assuming the hamsters don't eat the style.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Yeah,
overlineworks too."One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
-
It depends if you measure them or not.
cheers Chris Maunder
I can't be bothered with such fiddling small change.
-
Must...refrain...from...New Zealand...joke....
cheers Chris Maunder
Oh please !!! DO IT!
I'd rather be phishing!
-
C'mon - quatre vingt dix rolls off the tongue! (and it's the reason I can only count to 69 in French when I'm drunk. The maths gets too hard)
cheers Chris Maunder
It's easier in Switzerland, they use septante, octante, nonante instead of soixante-dix, quatre-vingts, quatre-vingt-dix. In Belgium they use some bastardised version with septante, quatre-vingt, nonante IIRC.
Wrong is evil and must be defeated. - Jeff Ello
-
Eddy Vluggen wrote:
It's also a nice shortcut, to change the display from msec to sec, just by setting this constant to "0" instead of "1000" :p
Depending on the usage you might then get a "Division by zero" exception / fatal error popup window instead.
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
Relatively speaking, without it, how could you ever know that your MILLISEC_PER_SEC doesn't match mine? :|
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
I actually disagree; I often deal with code using second, milliseconds, microseconds and even nanoseconds, sometimes with more than one unit in a function. Having a const (of some sort) declares what conversion was intended.
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
But what about ONE_SECOND_MS ?
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Surely that's a constant?
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
But you wouldn't believe how many people talk about 'kWh per hour' Sure, it could be meaningful if the power varies, but then 'kWh per hour' might vary, too, and cannot be treated as a single value. And lots of people refer to kWh/hour even when the power is constant.
-
I put it to you that a variable, constant or define named "MILLISEC_PER_SEC" is never, ever, ever needed.
cheers Chris Maunder
-
Or, perhaps it's needed to differentiate in regions where they use an Imperial Second instead of a regular one.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Like a dueling second?
-
Is that a leading question?
-
Is that a leading question?
-
I suppose that's the long and short of it.
-
I actually disagree; I often deal with code using second, milliseconds, microseconds and even nanoseconds, sometimes with more than one unit in a function. Having a const (of some sort) declares what conversion was intended.
A counterargument. Excellent. My counter-counter argument, and the reason my brain popped: I would always prefer to have something like
var timeInSeconds = X;
var timeInMilliseconds = timeInSeconds / 1000;My point is that the 1000 is always 1000. The variables surrounding that should be the ones clearly named. The "1000" can never be anything other than 1000. At least that's what I think.
cheers Chris Maunder
