Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!husc6!m2c!wpi!jhallen
From: jhallen@wpi.wpi.edu (Joseph H Allen)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Turbo C or MSC
Message-ID: <10378@wpi.wpi.edu>
Date: 29 Mar 90 17:03:32 GMT
References: <924@ns-mx.uiowa.edu> <1468@watserv1.waterloo.edu> <9944@pyr.gatech.EDU> <35104@cci632.UUCP> <2602972a.42b0@polyslo.CalPoly.EDU> <1990Mar26.154024.11739@dasys1.uucp> <1990Mar26.174313.1976@eng.umd.edu> <4548@daffy.cs.wisc.edu>
Reply-To: jhallen@wpi.wpi.edu (Joseph H Allen)
Organization: Worcester Polytechnic Institute, Worcester ,MA
Lines: 18

In article <4548@daffy.cs.wisc.edu> schaut@cat9.cs.wisc.edu (Rick Schaut) writes:
>As far as speed of the resultant program is concerned, MSC 6.0 has Watcom on
>the run.  It's impressive.  However, there is one other plus for MSC.  Since
>ver 5.0, the compiler has generated re-entrant code (i.e. code that will
>run in protected mode).

Is this for real?  What about returning structures?  Every compiler I know of
puts returned structures in a global variable.  It would make sense to just
stick it on the stack, but I think this might have some portabilty
consequences.  Does this compiler actually do this?  Or does being able to run
in protected mode mean something else...  (why should you need reentrant code
to run in protected mode anyway?) 



-- 
            "Come on Duke, lets do those crimes" - Debbie
"Yeah... Yeah, lets go get sushi... and not pay" - Duke