Xref: utzoo comp.sys.mac.programmer:1963 comp.lang.c++:1402
Path: utzoo!attcan!uunet!husc6!rutgers!apple!dan
From: dan@Apple.COM (Dan Allen)
Newsgroups: comp.sys.mac.programmer,comp.lang.c++
Subject: Re: AT&T C++ ports to the Mac?
Keywords: Aztec C
Message-ID: <15236@apple.Apple.COM>
Date: 7 Aug 88 03:12:21 GMT
References: <325@intek01.UUCP> <1479@mcgp1.UUCP> <561@helios.ee.lbl.gov>
Reply-To: dan@apple.apple.com.UUCP (Dan Allen)
Organization: Apple Computer Inc, Cupertino, CA
Lines: 16

In article <561@helios.ee.lbl.gov> beard@ux1.lbl.gov (Patrick C Beard) writes:
>LSC can accept variable names that are very long, I think basically of
>unlimited length.  It can generate inline assembly code for those tight
>spots.  It has a source level debugger.  MPW C can do none of these
>right now.  If I was given the job to port cfront.  I would do it in LSC.

Cfront has been ported via MPW C for almost a year now.  MPW 3.0 will
feature a source level debugger.  MPW C does not need to generate inline
assembly code because MPW includes a top-notch assembler as a standard
tool.  It assembles at over 40,000 lines/minute.  And MPW C can handle
very long identifiers as well.  Apple's MPW C++ in in Beta test
currently and will be available Real Soon Now.

Dan Allen
Software Explorer
Apple Computer