From: use_my_alias_here@hotmail.com   
      
   >> I asked the question because I believe that Microsoft is being   
   >> somewhat untruthful when they persist in calling C++/CX or C++/CLI or   
   >> C++/whatever "C++".   
   >>   
   >> It is not. And it is harmful to the integrity of C++ to do so, IMHO.   
   >>   
   >> If it were C++, I would be able to compile it with my   
   >> highly-accommodating C++ compiler.   
   >>   
   >> Microsoft has been, for years, attempting to mislead C++ programmers   
   >> into thinking that their "variants" of C++ is essentially C++ with a   
   >> bit of flavoring. ...   
   >   
   > IMHO this is just hair splitting. It's C++ with extensions, what else   
   > would you call it?   
   >   
      
   I guess the problem isn't that Microsoft supports C++ with extensions, the   
   problem is that you can't compile portable code for the Microsoft platform   
   because they have flavored their C++ with various mandatory unstandardized   
   extensions like ___stdcall.   
      
   Hopefully all future C++ extensions will be optional on all platforms,   
   otherwise the portability of C++ will be gone.   
      
      
   Regards,   
   Daniel   
      
      
      
      
   --   
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)