Managed C++ Hasn't Got Any Friends!
While Managed C++ is, for the most part, easy to use (probably easier than pure C++ itself), it buys this by making some sacrifices. There are, therefore, some really annoying facets of the language:
Managed C++ has no friends. This might seem a minor thing, especially since use of the friend keyword is so rarely useful or justified in pure C++. However, there are other restrictions of Managed C++ that conspire with the lack of friendship to create a real wart. Take the SID class. Its constructor (which takes void*) is visible because we have to be able to make SID instances from within the ACE, AccessToken, and GroupList classes. We most certainly do not want any code outside of this library to ever call that constructor. However, if I make the constructor private, the other classes cannot see it. If I try to make them friends, I'm given a C3809 and told to go away. I even tried placing the address of a private static creator method in a public function pointer within a static (class) constructor, but this was disallowed because it violated accessibility to managed types from unmanaged types. Unless Managed C++ supports the Assembly or Family and Assembly accessibilities which it does not, as far as I can discover then we're stuck with situations such as that with SID(void*). What's a J# client going to make of that?!
I mentioned in the article "Win32 Security in Managed C++" that we can conversion-construct managed enumeration instances from native types, which is very open to abuse. Given that, it is strange that, even in Managed C++, we cannot define constructors for value types. The LUID type, which is defined as:
public __value struct LUID
void Assign(::LUID const &rhs)
this->LowPart = rhs.LowPart;
this->HighPart = rhs.HighPart;
has to use the Assign method because we cannot define a constructor to instantiate it from the Win32 LUID structure. I presume there's a good reason, but it's annoying nonetheless.