awol@infopls.UUCP (Al Oomens) (10/30/90)
Does anyone have any info (benchmarks?) on diferances between MicroSoft Pascal versus Turbo Pascal? Execution speed, generated code size etc. Any info or oppinions would be appreciated! Al
bobb@vice.ICO.TEK.COM (Bob Beauchaine) (10/31/90)
In article <PgiTR1w163w@infopls.UUCP> awol@infopls.UUCP (Al Oomens) writes: >Does anyone have any info (benchmarks?) on diferances between MicroSoft >Pascal versus Turbo Pascal? Execution speed, generated code size etc. Any >info or oppinions would be appreciated! > Al Al: (The following refers to Microsoft Quick Pascal, 1.0) A satisfied Turbo Pascal user for several years, I attended a demon- stration of MS Pascal about a year and a half ago. I was impressed enough with the user interface to purchase the product. That turned out to be the last good impression I had of the language. Some of what I found: 1. The link buffer for MS Pascal is always the disk, so compile/link time to produce an executable suffers dramatically compared to Turbo (if you use memory linking with Turbo). 2. Generated code size was invariably larger, even with both compilers with full optimizations turned on. I have no benchmarks, but I have created hundreds of thousands of lines of code in Pascal, and every program I converted to MS Pascal was larger. 3. Execution speed was invariably slower, *especially* disk access. Again, no benchmarks, but the difference was *extremely* noticeable. 4. MS Pascal won't compile an executable larger than about 200k. 5. The environment proved to be quirky, and I often got errors with little more than a number and a message to call the Microsoft Product hotline. Not even so much as a probable cause could be gleaned from the display. 6. The only other good note: The Microsoft graphics kernel is included with Quick Pascal. This kernel has routines to handle automatic screen sizing and data scaling, releiving the programmer of some tedious programming. My advice: Stick with Turbo, at least until Microsoft addresses some of these problems with a future release. Borland has a much more polished product. ================================================================== Bob Beauchaine bobb@vice.ICO.TEK.COM (####) (#######) (#########) (#########) (#########) (#########) __&__ (#########) / \ (#########) |\/\/\/| /\ /\ /\ /\ | | (#########) | | | V \/ \---. .----/ \----. | (o)(o) (o)(o)(##) | | \_ / \ / C .---_) ,_C (##) | (o)(o) (o)(o) <__. .--\ (o)(o) /__. | |.___| /____, (##) C _) _C / \ () / | \__/ \ (#) | ,___| /____, ) \ > (C_) < /_____\ | | | / \ /----' /___\____/___\ /_____/ \ OOOOOO /____\ ooooo /| |\ / \ / \ / \ / \ / \
kamal@wpi.WPI.EDU (Kamal Z Zamli) (10/31/90)
In article <PgiTR1w163w@infopls.UUCP> awol@infopls.UUCP (Al Oomens) writes: >Does anyone have any info (benchmarks?) on diferances between MicroSoft >Pascal versus Turbo Pascal? Execution speed, generated code size etc. Any >info or oppinions would be appreciated! > Al Check out PC WORLD Sept 1989: Article title :" Turbo Pascal meets the Quick Challenge" Summary of the article: Turbo Pascal: Pro: -Object oriented implementation superior over Quick Pascal -Compiles to memory -Smart linking : smaller "exe" -Debugger : Turbo Debugger support Contra: -Can't edit multiple files Quick Pascal Pro: -Edit Multiple files -Graphics supriority: It clones all the turbo pascal graphics functions and procedures.Ability to set VGA pallette even in Text mode. -Mouse support -Emulates a lot of editors like brief etc.... Contra: -No other supporting debugger i.e Code View -Can't create overlays Conclusion of the article: Turbo Pascal is superior than Quick Pascal....
mead@uxh.cso.uiuc.edu (10/31/90)
RE the PC WORLD Sep 89 article, there are bench marks and although I'd say the two were within "spitting distance," TP55 is the clear winner. TP's smart linking wasn't mentioned, I'd heard that Microsoft pascal (not QuickPascal per se) loaded all code in a unit even if only one procedure was called. QuickPascal's editor is nicer--lets you customize it a good deal (EMACS,Brief,...) -alan mead : mead@uxh.cso.uiuc