I think it was in one of the On the Metal interviews where one of the guests mentions MPW was a submarine project, from UNIX background engineers, to eventually replace Pascal with C++.
Well they did exactly that - rewriting the Finder in C++, etc.
But it's unfortunate that losing Pascal/Object Pascal also meant losing bounded strings and array bounds checking, even if people turned the latter off in the 1980s because they thought that the performance cost wasn't worth the reliability improvement. That was probably the wrong trade-off then (at least for most regular application code) and even more so today (especially for the vast amount of legacy C code.)
> MPW was a submarine project, from UNIX background engineers, to eventually replace Pascal with C++.
According to Wikipedia, the first commercial C++ implementation came out in October of 1985, MPW was released in September of 1986, and MPW C was released in July of 1987.
C++ seems to have been added sometime in ~1988 (??)
Think C 4.0 (later Symantec C/C++) with (C++ like) object extensions seems to have been released for the Mac in 1989.
I was just trying to put the timeline together, as C++ doesn't seem to have been particularly production-ready when MPW was released (though I could imagine it had fans anyway.) Also Think C has been mentioned on HN a few times.
I looked at the intro to some of the MPW C++ documentation (before posting above, thank you internet) and I think it said that MacApp could be used via the C++ to Object Pascal bridge and that a native C++ framework would be forthcoming.
Why is writing inline Assembly considered an advantage of C, a language extension even not part of ISO, and always used to point out issues when other languages make use of it?
Naturally there had to be a balance, until mid-90s what we consider AAA games, were mostly Assembly.
I think it was in one of the On the Metal interviews where one of the guests mentions MPW was a submarine project, from UNIX background engineers, to eventually replace Pascal with C++.