|
Or, if you're talking about the distaff side: vidi, vici, veni.*
* Not only Latin, but also semi-archaic English phrase usage -- it'll be sheer luck if anyone gets it
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The order of events always has been important and too early was never goos. 
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Gloria got sick on the bus Monday. 
|
|
|
|
|
That's how companies like MS keep pedaling worse and worse crap, "new version of windows" - and the lemmings dive in because 'newer means better and more features does it not?' Few read further to find out nothing great, useful features and control have been removed, and some of the 'new features' are actually downgrades of old better features, for example the one of the biggest downgrades: 'windows (pl)' became 'window (s)' albeit with a fast sounding new name 'metro'. Newer was definitely not better. (What's next? A console window only?)
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
Lopatir wrote: (What's next? A console window only?)
Retro Style, it's the future.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
|
You know, it really doesn’t matter what you write as long as you’ve got a young, and beautiful, piece of text. An 'extremely credible source' has called my office and told me that Lorem Ipsum's birth certificate is a fraud. You’re disgusting. Does everybody know that pig named Lorem Ipsum? She's a disgusting pig, right? An ‘extremely credible source’ has called my office and told me that Barack Obama’s placeholder text is a fraud.
The best taco bowls are made in Trump Tower Grill. I love Hispanics! I write the best placeholder text, and I'm the biggest developer on the web by far... While that's mock-ups and this is politics, are they really so different? We have so many things that we have to do better... and certainly ipsum is one of them. An 'extremely credible source' has called my office and told me that Lorem Ipsum's birth certificate is a fraud.
I’m the best thing that ever happened to placeholder text. Trump Ipsum is calling for a total and complete shutdown of Muslim text entering your website.
I don't think anybody knows it was Russia that wrote Lorem Ipsum, but I don't know, maybe it was. It could be Russia, but it could also be China. It could also be lots of other people. It also could be some wordsmith sitting on their bed that weights 400 pounds. Ok?
Does everybody know that pig named Lorem Ipsum? She's a disgusting pig, right? You're telling the enemy exactly what you're going to do. No wonder you've been fighting Lorem Ipsum your entire adult life. Be careful, or I will spill the beans on your placeholder text.
(This message was brought to you by Trump Ipmsum)[^]
|
|
|
|
|
No, this is not a programming question, just a curiosity.
So here I am with some nice working codez in Windows, which give the answer I expect.
I have dumped these wonder codez into Android, and it gives me the answer I expect.
But only because I am not looking at maximum precision.
An interim value, which I just happened to check, differs somewhat:-
Android = 0.16993027262751734
Windows = 0.169930272651588
The only difference is using \ in Windows and Math.Floor in Java. Although the calculation is somewhat long and complex, nearly all of it was just copied/pasted. However, it seems I am only getting 10 digit precision, instead of the minimum of 13 I expected from double.
This error could easily result in my attack ships not being correctly positioned at the Lagrange point off Orion's shoulder...
|
|
|
|
|
Where is it written that MMUs FPUs on different hardware/processors have the same precision?
And wait all you want at the main Lagrange point. I will use a weaker pirate point and spare my dropships[^] a few days flight time.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
CDP1802 wrote: Where is it written that MMUs FPUs on different hardware/processors have the same precision?
Yeah, verily I say unto thee, 'tis written in the Almagest, 64 bits is 64 goddam bits, and should be treated as such, whatever thou sayest. 
|
|
|
|
|
Ok, there is something written here[^] about that, but perhaps these are merely guidelines.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Yeah, well, the same worthy tome also says:-
This gives 15–17 significant decimal digits precision.
Right here![^]  
|
|
|
|
|
Merely guidelines.[^]
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
What is "\ in Windows"? VB's truncating division?
|
|
|
|
|
Yup - this is an old hobby project originally written in HP Basic for the HP95, and morphed through various hardware incarnations over the years, so yes, it is the VB integer division sign, although I first used it in good ol' Fartran, sorry, Fortran.
|
|
|
|
|
Well, I don't get it. While there are differences between truncating division and division followed by floor, none of them seem like an immediately obvious culprit. Then, without context it's hard to tell.
- VB's \ will first round its inputs to integers, then divide them with truncation. The initial rounding makes it different, and it will do weird things if the input is outside of the range of an integer, but then you would have a total BS result and you don't.
- division-followed-by-floor means the division first rounds (not to an integer, but to the nearest double) and then it goes down instead of towards zero (so for negative results it's usually different by 1).
And then there's the usual "floating point stuff that runs on x86 will probably use x87 and its weird 80bit floats" thing that likes to mess things up unpredictably.
|
|
|
|
|
You could still watch C-beams glitter in the dark near the Tannhäuser Gate.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Now, you would not be an android that dreams of electronic sheep?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
All those moments will be lost, in time. Like tears, in the rain.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You should listen to the rhythm of the falling rain...
(a quick change of subject and genre)
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
If you really want an answer you should provide more information which will make it then a programming question.
When performing complex calculations, small differences can accumulate. You might check all interim values to know where it happens.
A possible reason might be that x86 math operations using the math coprocessor (AKA x87) are performing all operations internally with their 10 byte format and convert the result to single or double precision with proper rounding upon storing to a variable in memory.
The floating point units of other CPUs - and the vector units of x86 CPUs - are using only single or double precision where the result of operations are not rounded.
|
|
|
|
|
To be honest, I am not really surprised at the difference. It represents less than 100 milliseconds over a century, and as I am only interested in half a second per day, it is irrelevant.
I may bother to track it down sometime, but since the process goes through well over 100 trig functions, all with a multiplier 'inside and outside' as it were, which are subtracted and/or added to each other, through multiple iterations, it would take more time than it's worth.
|
|
|
|
|
Half a second per day can become quite much while time goes by 
|
|
|
|
|
True, but my half-second-per-day only relates only to UTC for the particular day in question.
The referenced calculation is a step in the determination the rotation of the foci of the earth's orbit against the background stars - not a lot!
|
|
|
|
|
Then you might have the explanation as also said below by Harold:
The x87 has build-in trigonometric functions (with proper rounding as already noted) while libraries are used with CPUs that did not have these built-in.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
