Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!se-sd!dennis
From: dennis@se-sd.sandiego.ncr.com (Dennis Foster)
Newsgroups: comp.windows.ms
Subject: Re: Real, I mean REAL Neophyte!
Keywords: TurboC
Message-ID: <1855@se-sd.sandiego.ncr.com>
Date: 18 Mar 89 22:28:11 GMT
References: <590@pacsbb.UUCP> <8002@ihlpf.ATT.COM>
Reply-To: dennis@se-sd.sandiego.NCR.COM (Dennis Foster(AEP))
Organization: NCR Corp. Systems Engineering, San Diego
Lines: 11

In article <8002@ihlpf.ATT.COM> michael1@ihlpf.UUCP (00771a-Pula,M.K.) writes:
> ... stuff deleted ...
>  I'm fairly proficient in MS assembler, but don't look forward to
>  developing my whole application in it.  Is there any reason why
>  TurboC cannot be used to develop MS windows applications or do you
>  HAVE to use MS C?

To write MS Windows applications, you need a compiler that can generate
windows compatible calling sequences.  Currently, the only ones I know of
are MS C and MS Pascal.  If Borland enhances their TurboC to
support the MS Windows calling conventions, you can use it.