mebhl@cc.nu.oz.au (11/15/90)
I've been looking at the Apple DTS Sample Code available from various FTP sites. Some of it appears to do things I want to do. Is there any great difficulty in porting to THINK Pascal from MPW ? I think I can handle different compiler directives and Uses clauses OK. Some bits that I see as potential stumbling blocks are expressions such as: gdFlags := 2 ** noDriver; (so what is the ** operation?) from offscreen.incl.p in SC.016.OffSample. And what to do with the assembly code in the UFailure unit, also in SC.016.OffSample ? Or should I just be getting general ideas from this code, without wholesale porting ? Thanks for any comments or advice. ---------------------- Peter Lewis mebhl@cc.nu.oz.au Mech. Eng. University of Newcastle NSW AUSTRALIA 2300
Chris.Gehlker@p12.f56.n114.z1.fidonet.org (Chris Gehlker) (11/20/90)
In message <4057.2742c610@cc.nu.oz.au> mebhl@cc.nu.oz.au(Peter Lewis) asks: > I've been looking at the Apple DTS Sample Code available from various > FTP sites. Some of it appears to do things I want to do. > > Is there any great difficulty in porting to THINK Pascal from MPW ? > I think I can handle different compiler directives and Uses clauses OK. Don't forget the Pascal source converter on disk 5. It's documented in Chapter 20 in the main manual. > Some bits that I see as potential stumbling blocks are expressions > such as: > > gdFlags := 2 ** noDriver; > > (so what is the ** operation?) It's the FORTRAN exponentiation operator that snuck into MPW Pascal by way of VAX Pascal. Use XpwrI > Or should I just be getting general ideas from this code, without > wholesale porting ? Port it. I've found that it's pretty easy to write portable code with judicious use of the the {$IFC} and {$ELSEC} compiler directives. -- Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!56.12!Chris.Gehlker Internet: Chris.Gehlker@p12.f56.n114.z1.fidonet.org