Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!evax!utacfd!letni!rwsys!spudge!johnm
From: johnm@spudge.UUCP (John Munsch)
Newsgroups: comp.windows.ms.programmer
Subject: Re: BC++ and MSC SDK...
Message-ID: <28201@spudge.UUCP>
Date: 6 Mar 91 15:02:21 GMT
References: <27180@uflorida.cis.ufl.EDU> <2HcBy1w163w@bluemoon.uucp>
Reply-To: johnm@spudge.UUCP (John Munsch)
Organization: Friends of Guru Bob
Lines: 19

In article <2HcBy1w163w@bluemoon.uucp> andy@bluemoon.uucp (Andy Vaught) writes:
>Remember-- C compilers are almost always written in C themselves. The 
>usual development sequence would have Borland writting their compiler in 
>C, compiling with MSC. When debugged, the new compiler can be used to 
>compile itself, leaving behind its MSC heritage. Given that MSC was the 
>only way to write windows system programs, it seems highly unlikely that 
>the Borland developers could have used anything else. 

A good theory, if Borland C++ were a Windows system program.  It isn't.

It's the same old IDE as we saw in Turbo C++ v1.0 with a few modifications
so it can spit out Windows compatible executables.  It seems unlikely that
the IDE was done in MSC because it utilizes VROOM.  Also, I've seen the
compiler run, it's too fast to have been written in Microsoft :-).

As for the Whitewater Resource Toolkit, I would guess that it is written in
Actor.  Never having used Actor though I could be very wrong.

John Munsch