It's not Google's fault. ARM defined the EABI stack unwinder strangely. Android didn't support exceptions at first.https://twitter.com/RichFelker/status/711009996419559425 …
-
-
.
@RichFelker Google didn't use SJLJ for Android. I misread the headers. Google didn't support C++ exceptions in the NDK API until later. -
.
@RichFelker The worst C++ ABI for ARM was Symbian. They used an ancient version of GCC, rolled their own SJLJ-style exceptions with macros. -
.
@RichFelker My basic complaint with Android is it's "the revenge of BeOS". They forced Java on developers, just like BeOS forced C++ APIs. -
.
@RichFelker Two basic complaints with BeOS in 1997: 1) the fragile base class problem, which they solved by padding public C++ classes. -
.
@RichFelker 2) BeOS forced developers to use threads, which led to tons of race conditions. Each BWindow needed its own event loop thread. -
.
@RichFelker So my impression of Android is: ex-Be devs (Travis Geiselbrecht, Dianne Hackborn, et al) rewrote BeOS in Java instead of C++. -
.
@RichFelker The major architectural difference was to use a single UI event thread, just like every other GUI API that became successful. -
.
@RichFelker My major complaint with Android is that all apps are forced to run the Java VM in user space to interface with the system. - 17 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.