Note also that it's not just a compiler to compiler difference in the typeid names. They differ from one compiler version to the next compiler version. So if you want consistent names, you either create them yourself, or use demangling utilities.
My original prototype was demangling the values in an attempt to make them standard. I was using a different method than typeid().name(), but it looked like either method could work, with typeid().name() being the better method. It was just going to be a lot of compiler specific code. I've since found a different way to solve my problem that doesn't use string descriptions of the type, but I do think it would be nice to have a library that will give you the same string across supported compilers (at least wherever possible). Jared