I’d like to thank Yves Dolce for responding to Wesner Moise who writes: Sender: Wesner Moise re: Value Type Representation Between the Original and Revised C++ I am not sure that I understand you when you say v.ToString() results...

For the work I’ve been engaged in currently in machine translation of the original language design [thing1] to the revised design of the language [thing2], I have been variously making stabs at understanding the possible usages of a managed Value...

Program efficiency at the programmer level is something of a complicated issue – in part because it is contextual. That is, it is hard to say something that holds true in all cases. [This is why having a good profiler is essential.] For example...

The declaration of a managed array object in the original language design was a slightly non-intuitive extension of the standard array declaration in which a __gc keyword was placed between the name of the array object and its possibly comma-filled dimension...

A reader, Yves Dolce, writes: Related to your last blog entry: The Astonishing S"Literal" String Type I was surprised that sometimes, boxing is conceptually implicit... That any Object method can be called directly without any explicit boxing...

indranil banerjee writes re: Virtual Function Behavior Between ISO C++ and C++/CLI Revisited Thanks for the explanation. Rereading your earlier post and examples, it is quite clear that runtime resolution of virtuals is the same in both CLR...

One of the astonishing infelicities of the original language design was the unflagged overhead of the seemingly trivial failing of placing an S in front of a string literal targeted to a managed reference object. For example, given the following two System...

I seem to have rather badly explained the `virtual function invocation within a constructor issue,’ if one is to judge by the following question posted as a follow-up to my blog entry, for which I apologize: Sender: Indranil Banejree ...

I received the following mail the other day in response to my writing that the Visual C++ compiler has [finally!] implemented the name return value optimization (NRVO) in the Visual Studio 2003 release: Sender: James Slaughter I was in the...