Well, I see no reason why a native C++ statement would pass just fine in a native build but would flag a syntax error with the /clr switch. After all the code is native in both cases and c++/cli is supposed to accommodate native c++ syntax. So that is a complier issue!
Right now there are a host of errors associated with functions having no return types (really poorly written code) but returning a value. This passed by native VC C++ build without a hiccup but as soon as the /clr switch is on these statements were all flagged as errors by VC.
The errors for this are,
error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
So if C++ doesn't support default int and int is assumed then how did this get past the native compiler?
So that isn't a compiler problem????