![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png) cartesiandaemon.livejournal.com |
Fri 2013-07-12 15:02 |
Yeah, that seems like a good list :)
I was about to say, it's possibly surprising more languages aren't designed to compile to C, and then let the C compiler writers do all the heavy lifting of making them fast on every platform. But I guess I've just reinvented Java, oops :)
hybrid eg. GC with an optional explicit free operation which causes an allocated thing to become instantly invalid
Yeah, except I always think the of reverse: it seems most variables go out of scope at fairly clearly defined places, and I've grown very fond of having RAII work the C++ way (always) rather than the C# way (every time you use a IDisposable class, you can be leak-safe and exception-safe, provided you remember to add the "don't leak this" boilerplate). But it would be nice to have a garbage collector for things left over. Although I suppose the GC needs to be aware of any other variables which might still hold a pointer to them. |
|
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}