Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Questions about THINK C v4.0
Message-ID: <2418@husc6.harvard.edu>
Date: 11 Aug 89 14:59:35 GMT
References: <9878@phoenix.Princeton.EDU>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 38

In article <9878@phoenix.Princeton.EDU> bskendig@phoenix.Princeton.EDU (Brian Kendig) writes:

>I've heard a lot of speculation about what it does and doesn't support.
>From what I can gather, it can handle both C code and C++ code.  Is this
>correct?  If it can still handle straightforward C (why wouldn't it?),
>can it deal with ANSI C, or are we still stuck with 'old-style' C?

	THINK C 4.0 will not compile ALL C++ code, only a subset, which
encompasses the core object-oriented extensions. (The extensions are
analogous to Object Pascal.)

>Is it compatible with projects constructed by earlier versions of THINK C

	Yes; one caveat, though - the standard libraries have been rewritten
for ANSI conformance, and the organization and names of header files have
been changed substantially.

>And what are its assembler capabilities?  Does it have a (good) in-line
>assembler?

	A full 68K/68881 assembler is supported inline, and it allows
transparent access to C symbols; it also incorporates some of the compiler's
branch and label optimizations, and a few others.

R.


~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"When it comes to my health, I think of my body as a temple - or at least
a moderately well-managed Presbyterian youth center." - Emo Phillips

~~~~~~~~~~~~~~~