I think it's simply an old list...if you look modern OS X stack traces, you often see C++ names in various frameworks. Random ones I found in `Console.app` (sadly this is a rather new & stable system):
I think I even saw a core part of NSAutoreleasePool in there once. I have never read the public Apple source tarballs, but from just seeing stack traces every now and then, it seems as if Apple is very happy with using both Objective C and C++ (the compiler makes this easy of course - e.g. C blocks have support for C++ construction/destruction etc...).
> TCharStreamCFString::~TCharStreamCFString() + 37 (CoreText) [0x7fff9454b091]
> JSC::BlockAllocator::blockFreeingThreadMain() + 90 (JavaScriptCore) [0x7fff950fad0a]
> CA::Render::Server::server_thread(void) + 403 (QuartzCore) [0x7fff8c6e435b]
> TFSInfo::FetchProperties() + 1274 (DesktopServicesPriv) [0x7fff93a7da20]
> 0x000000010b50afca ld::tool::InputFiles::forEachInitialAtom(ld::File::AtomHandler&) + 410
Same on iOS...
> CoreMotion 0x043d60a2 CLMotionCore::runMotionThread(void) + 1016
I think I even saw a core part of NSAutoreleasePool in there once. I have never read the public Apple source tarballs, but from just seeing stack traces every now and then, it seems as if Apple is very happy with using both Objective C and C++ (the compiler makes this easy of course - e.g. C blocks have support for C++ construction/destruction etc...).