home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!usc!rpi!uwm.edu!psuvax1!atlantis.psu.edu!apix.psu.edu!thor
- From: thor@vivaldi.psu.edu (Thomas Moertel)
- Subject: What are Apple's future plans for C++ and MacApp?
- Message-ID: <THOR.92Aug26234612@haydn.vivaldi.psu.edu>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Pennylvania State University
- Distribution: comp
- Date: 26 Aug 92 23:46:12
- Lines: 31
-
- The folks at Apple have done a wonderful job with MPW C++ 3.2, but I
- can't help but be envious of my MS-DOS friends who have C++ compilers
- that compile directly into native code, support templates, and support
- exception handling. I'd hate to think Apple was losing developers
- because their development tools are a behind the times (e.g., cfront
- 2.1). I can't find anything on ETO#8 that indicates either templates
- or exception handling will be in any near term MPW C++ release. Even
- worse, I've heard net chatter saying that Apple's new Lucid C++
- compiler will be without templates and exceptions, as well. Can this
- possibly be true? (Please say it's not. ;-)
-
- With this in mind, can anybody tell me what Apple's near- and
- long-term plans are for C++?
-
- And because I'm really curious, how will MacApp fit into the new C++
- picture? With C++ compiler support for exception handling, the
- TObj::Initialize() and TObj::IObj() methods, as well as FailInfo-based
- exception handling, could be a thing of the past. (wow!)
-
- Please, somebody tell me I'll have a mighty C++ compiler with
- templates and exception handling in the near future. (I don't know
- how I'll ever convince my DOS-based developer friends to even *look*
- at a Mac without a top-notch C++ compiler.)
-
- Thanks in advance for any info or uncanny predictions!
-
-
- --
-
- Tom Moertel Pennsylvania State University
- thor@vivaldi.psu.edu "Them bats is smart. They use radar!" ;-)
-