4 ms·
> Turbo Pascal programs start by calibrating a delay loop (so that the Delay function knows how much to spin to achieve a certain delay). The calibration counts
by Wowfunhappy 7y ago
> Turbo Pascal programs start by calibrating a delay loop (so that the Delay function knows how much to spin to achieve a certain delay). The calibration counts the number of times a certain loop is run for 55ms (as measurable using the PC’s timer interrupt with its default setting), then divides the number of loops by 55 so that Delay can then busy-wait in millisecond increments.
Why not use the PC's timer interrupt for the delay function itself?
- 0x0 7y agoMS-DOS kinda expects the timer interrupt to only fire at around 18.2hz I think so it's too coarse for millisecond delays.
- mailslot 7y agoI always assumed it was 16hz. Oh well. That was a long time ago.
- bonzini 7y agoYou can read the timer's countdown counter instead of relying solely on the tick; it runs at 1.2 MHz approximately.
- rasz 7y agoms dos compatible != IBM PC compatible. 80186 based PC will still run TP programs, despite Timer0 being mapped to port 30-36H instead of 40-43H, not to mention totally non 8253 compatible.
- pdw 7y agoTurbo Pascal is old enough that (I think) they probably wanted to keep compatibility with machines that ran MS-DOS but weren't IBM PC-compatible. If that's the case, messing with the timer interrupt would've been a bad idea.
- bonzini 7y agoNah, this is TP7 and it already was exclusively for PCs. I think 3.0 was the last version that was ported to other systems.
- IshKebab 7y agoBecause your delay resolution is then 55 ms, and accuracy is plus or minus 55 ms, and using interrupts is really complicated.
- CamperBob2 7y agoThe 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.
- Someone 7y agoNo 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 https://en.wikipedia.org/wiki/Pentium_Pro)
- badsectoracula 7y ago> 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.
- rasz 7y agoI 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.