rodzimguitar68
Fractal Fanatic
What does NaN stand for?
EDIT: Googled it, "Not a number" is that right?
This will give you the info you are looking for:
What does NaN stand for?
EDIT: Googled it, "Not a number" is that right?
This sounds like a great excuse to crank up the Uber model today
Aussie here. It's interesting to me as I've realised while teaching my kids to read that often the American way of pronouncing things is more phonetic, compared to the Aussie way. I've grudgingly had to accept that the American way is often more sensible. But then the American way of saying Beta with a crazy "AY" sound instead of the more obvious phonetic "E" is an exception in the other way.
Given that he already diagnosed the issue, and that fixing a NaN is usually a trivial endeavor, I'd say either he's decided to rewrite the affected code instead of just doing a quick fix, or is busy hacking away at other bugs or a new feature. I'm sure we won't have to wait too long until we find outI’ll bet Cliff comes back with not only the bug fix but also with new toys.
Given that he already diagnosed the issue, and that fixing a NaN is usually a trivial endeavor, I'd say either he's decided to rewrite the affected code instead of just doing a quick fix, or is busy hacking away at other bugs or a new feature. I'm sure we won't have to wait too long until we find out
Queue all the smarty pants' telling us how hard NaNs can be to diagnose and fix in 3, 2, 1...Given that he already diagnosed the issue, and that fixing a NaN is usually a trivial endeavor, I'd say either he's decided to rewrite the affected code instead of just doing a quick fix, or is busy hacking away at other bugs or a new feature. I'm sure we won't have to wait too long until we find out
Sometimes it is the compiler creating the NaN
I know this was an issue with the FM3, don't recall it being a problem with the IIISometimes it is the compiler creating the NaN, and they have to program around how the compiler is interpreting the code to create the executable and creating the NaN issue.
It's not a compiler issue. It's a PEBKAC.
Well, I was going to tell a SOC7 anecdote...Queue all the smarty pants' telling us how hard NaNs can be to diagnose and fix in 3, 2, 1...
I just cringed a littleWell, I was going to tell a SOC7 anecdote...
Oof, that stings. Too close to home. Lots of stuff here has managed to find /dev/null that used to be stored in RAM, and randomly placed extraneous do...while loops have appeared in the code....My system tends to throw ID-10-T errors with increasing frequency these days. It's a combination of memory errors and slowing processor performance.
ROTFL I thought I knew most common acronyms, but this was a new one for me. So I looked it up:
"Short for problem exists between keyboard and chair, PEBKAC is a term used by computer technicians and IT professionals to describe a user error. The term asserts that the user is to blame when referring to the technical issue at hand; not the installed software or the device itself"
Good one, Cliff