I Love that New Syntax Smell

First, I should apologize for the lack of postings lately.  A combination of server downtime/outages and apathy have kept me from making postings.  Now that we're back up, I think I should clarify some of what I've said. Value types aren...

A while back, in order to get some code to compile, I had to update PtrToStringChars (found in vcclr.h) to work in the new Whidbey C++. In case anyone wants this, I've posted my implementation (and a small main() to drive it) here: p2sc.zip . ...

I was going to give a short introduction to the C++ handle (^) today.  But, Brandon did such a good job, I think I'll just link to his article .

We've got a code sample today, of a simple integer stack implemented using Whidbey C++.  I'll implement it using three pieces of code: stack.h - definition of the stack stack.cpp - implementation of the stack main.cpp - driver...

Last time, I discussed the ref type .  This time, I'm going to talk about the value type.  This is the CLR type exposed in Managed Extensions by the __value keyword, and available in Whidbey C++ using the context-sensitive keyword value...

There are two major CLR types that we expose in Whidbey: ref and value . I'll talk about ref types here, and about value types later. So, what is a ref type?   This is the same type that was exposed in Managed Extensions as __gc . ...

If you've used Managed Extensions, you're familiar with the CLR types that __gc and __value exposed.  These have now been replaced with the context-sensitive keywords ref and value . Context-sensitive keywords?   That's right. ...

...or, "Hey! My data ain't garbage!"...

...or, "Do we really need another blog?"...