Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!news From: melling@cs.psu.edu (Michael D Mellinger) Newsgroups: comp.sys.amiga.advocacy Subject: Re: NeXT Press Release Message-ID: Date: 25 Apr 91 23:15:35 GMT References: <47889@ut-emx.uucp> Sender: news@cs.psu.edu (Usenet) Organization: Penn State Computer Science Lines: 28 In-Reply-To: greg@ccwf.cc.utexas.edu's message of 25 Apr 91 16:22:35 GMT Nntp-Posting-Host: sunws5.sys.cs.psu.edu In article <47889@ut-emx.uucp> greg@ccwf.cc.utexas.edu (Greg Harp) writes: Well, for one thing C++ is standard. I don't use non-standard languages unless I _know_ I'm not going to be porting something. On the NeXT, I can't assure that, even if I'm using DP for something. Using a non- standard language on _any_ Unix box is not a very smart thing to do. Who's to say that you _won't_ port it, re-writing the GUI code for the other platform? The IBM PC is standard why don't you use it? Standard does not imply better. Anyway you can program using C++ on the NeXT, if you so desire. A C++ compiler is include free when you buy the NeXT(didn't I mention this before). Of course, NeXT went and stuck you with Obj-C if you want to use their Interface Builder. It'd be nice if you could select the language like most other interface design packages I've used. So, don't use the IB. You can program the old fashion way if you want. You can write the biggest part of your code in C++ and write your interface code in Objective C too. Sorry, but C++ doesn't have the ability to dynamically load objects at run-time. The other IB's generate code. On the NeXT, binary files are generated that you never look at. -Mike