3 ms·
The thorough seeding of the list with defunct examples (BeOS, Mac OS < X) gives off a weird vibe. There's also the standard halo effect listing. Any sufficient
by jacques_chester 14y ago
The thorough seeding of the list with defunct examples (BeOS, Mac OS < X) gives off a weird vibe.
There's also the standard halo effect listing. Any sufficiently large company is using a language / methodology / philosophy / technology you've heard about. And they're being namechecked on that language / methodology / philosophy / technology's website.
The classic is Microsoft.
Did you know Microsoft uses Scrum? They do!
Did you know Microsoft uses ISO 9295-424:54 (Humungo Software Dev Standard Written by the SEI, the DoD and a committee of 200 researchers from different Fortune 50 companies)? They do!
(Hint: Microsoft doesn't have a single unified method of development, it's largely up to each section to decide how they do the work)
- cturner 14y agoBeOS is interesting partly because of how it limited use of C++. C++ was the only supported API for userland, but the kernel was C. Found a reference: "Creating a driver on BeOS is done using ANSI C; the C++ language requires certain support which is not available in the BeOS kernel environment." http://testou.free.fr/www.beatjapan.org/mirror/www.be.com/aboutbe/benewsletter/volume_III/Issue7.html#Workshop http://testou.free.fr/www.beatjapan.org/mirror/www.be.com/ab... I remember another newsletter article where one of the devs described techniques for getting C++-like power while remaining within C (heavy use of function pointers in structs, that kind of thing). Another: http://www.haiku-os.org/legacy-docs/benewsletter/Issue4-51.html http://www.haiku-os.org/legacy-docs/benewsletter/Issue4-51.h...
- leakybucket 14y agoThe BeOS userland api had base classes with reserved functions that were there solely to reserve space in the objects vtable becase of the fragile base class problem: http://en.wikipedia.org/wiki/Fragile_binary_interface_problem http://en.wikipedia.org/wiki/Fragile_binary_interface_proble... I wonder how modern C++ frameworks are handling this?
- gurkendoktor 14y agoI 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): > 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...).
- mikeash 14y agoAlmost the whole Objective-C runtime is C++ these days, although really more like C with occasional use of C++ features.