How should we declare and use a .NET reference type? It differs significantly from the C++ Object Model: different memory model (garbage collected), different copy semantics (shallow copy), different inheritance models (monolithic, rooted to Object, supporting single inheritance only with additional support for Interfaces).
Stanley Lippman has a blog, ee i
If you want to see the answer visit Stanley's next entry.
This might be a good time to point out that the Microsoft lingua-bloggers (e.g., Brad Abrams, Brandon Bray, Chris Brumme, Eric Gunnerson and Paul Vick) are changing the landscape of language design. More transparency, more community involvement, and perhaps most importantly for us: giving language design the status it deserves.
Note: I am no Microsoft fan, and the last sentence isn't intended to imply that the resulting languages are any good. Only that the process is a bit different than it was only a couple of years ago.
It is well worth asking whether language design benefits from this sort of openness, or whether a lone developer has a better chance of coming up with a coherent and usable language (think of your favorite language designer). Even if you favor openness, keep in mind that most programmers lack experience in language design. They may have good ideas for libraries, APIs etc. But do they really understand the implications of their suggestions on the compiler, the type system, or even on the run time system? Some obviously do. But aren't these the same people who were involved all along (via ISO, CS departmental seminars, conferences, etc.)?
Posted to cross-language-runtimes by Ehud Lamm on 12/2/03; 1:44:09 AM