News for hackers. Stuff that matters.
Re:Why did Turbo Pascal apps fail with a division-by-zero on... by IshKebab on Saturday August 24, 2019 @01:52PM (#20788573)
Because your delay resolution is then 55 ms, and accuracy is plus or minus 55 ms, and using interrupts is really complicated.
Re:Why did Turbo Pascal apps fail with a division-by-zero on... by CamperBob2 on Saturday August 24, 2019 @04:59PM (#20789672)
The slow timer actually works in your favor if you do it right. You don't count interrupts, you count CPU cycles between interrupts (search term: "reciprocal counter.")

This bug was just laziness on Borland's part; there were no excuses for it. There were any number of ways to do it correctly. Fortunately they fixed it pretty quickly, too. While I remember running into it, it wasn't a huge issue.

Re:Why did Turbo Pascal apps fail with a division-by-zero on... by Someone on Saturday August 24, 2019 @05:54PM (#20789962)
No excuse? It may have been a left-over from early versions.

The original Turbo Pascal ran on PCs of the day, running at 4.77MHz, and with 64 kilobytes of RAM.

Even if one foresaw computers running at 200MHz, I don’t think that, at the time, it was clear that a single architecture would stay around long enough for that to be a problem. The Pentium Pro peaked at 200MHz in 1995-8 or so, 12 to 15 years after the first release of Turbo Pascal (https://en.wikipedia.org/wiki/Pentium_Pro)

Re:Why did Turbo Pascal apps fail with a division-by-zero on... by badsectoracula on Saturday August 24, 2019 @08:37PM (#20790624)
> It may have been a left-over from early versions.

Earlier versions do not have this particular bug, it was introduced in version 7. However they have another bug which causes Delay to simply not work properly (it finishes quicker than requested) and most likely the changes in ver7 were made in an attempt to fix that one.

Re:Why did Turbo Pascal apps fail with a division-by-zero on... by rasz on Saturday August 24, 2019 @10:16PM (#20790935)
I think its the very same bug, they just bumped counter from 16 to 32 bit, but left the rest of logic intact, including 16 bits for the result of division.
Re:Why did Turbo Pascal apps fail with a division-by-zero on... by Someone on Sunday August 25, 2019 @05:16PM (#20795647)
Reading https://retrocomputing.stackexchange.com/a/12112, they moved the limit from ≈20MHz (num iterations overflowed 16 bits, leading to incorrect computation of the number of loops to run per second) to ≈200Mhz (num iterations divided by 55 overflowed 16 bits, leading to this “divide by zero” message)

(Aside: all things staying the same, that should have increased the limit by a factor of 55. It seems the processor got more efficient running these idle loops by a factor of about five (about 2½ if there’s a sign bit in the result of the division)

So yes, you could call this a different bug. I don’t think having that bug in the code is inexcusable, though.

TP7 is from March 1993 (http://progopedia.com/version/turbo-pascal-7.0), and it seems the first 200Mhz PC CPU was from November 1995 (https://en.wikipedia.org/wiki/Timeline_of_computing_1990–199...)

⇒ I don’t think they could have found this in testing. So, is it inexcusable that this went through code review? I don’t think so. Not only would one have to realize that that new limit now came into play, one also would have realized the higher efficiency of the 200MHz processor(s) would bring the number down further.