lsr@Apple.COM (Larry Rosenstein) (05/03/90)
In article <1990May2.071040.19290@agate.berkeley.edu> 39clocks@violet.berkeley.edu writes: > > Now if I am programming in C, why would I want Pascal? Because I want to > use MPW C++ interfaces to MACAPP so that I can write programs lickity-split > style. MACAPP, of course, is written in Pascal. Don't get me wrong, I You don't need Pascal to use MacApp from C++. The MacApp release comes with pre-built libraries (debug & non-debug versions) so that you don't have to build MacApp from the Pascal sources. You would need to build MacApp if you need some other configuration (68020 specific, for example), or you can get the MacApp CD-ROM, which comes with a wider variety of pre-built configurations (and is cheaper, I believe). > great (or so I hear), but the real issue here is that there is no comperable > object library available for MPW C++, _yet_! What's the issue? You can use MacApp from C++. There's no class library that specifically tailored to C++, but that's not much of an issue in using MacApp. You can take advantage of many of C++'s feature even if you restrict yourself to Object Pascal compatible objects, and you can still use "native" C++ objects in you program's internals if you want Larry Rosenstein, Apple Computer, Inc. Object Specialist Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr AppleLink: Rosenstein1