crassfool: You likely know how it is. You get a bug that you can't understand, that makes no sense at all, where the computer goes all haywire when your code is simple, straightforward, and everyone who looks at it says it's right. Might be a compiler bug, right? But if you come right out and call it that, somebody will immediately prove that it's not, it's an error on your part, and you're humiliated.I've seen probably more than my share of compiler bugs, but I'd do more testing before I was sure. It has probably been close to twenty years since I found a real one in an optimizer. In that case, the compiler did an invalid tail-recursion optimization. Shared storage between caller and callee (an array) made the optimization invalid, but it only blew up rarely (SMTP in my case).Particularly, I'd be confirming that the code is actually wrong in the structure access. That sounds like a too-well-known, too-critical location for a bug like that. There are lots of other subtle ways this could go wrong.rj
Best Of |
Favorites & Replies |
Start a New Board |
My Fool |
BATS data provided in real-time. NYSE, NASDAQ and NYSEMKT data delayed 15 minutes.
Real-Time prices provided by BATS. Market data provided by Interactive Data.
Company fundamental data provided by Morningstar. Earnings Estimates, Analyst Ra