From: Ferdinand P. <fer...@ix...> - 2004-04-16 11:00:30
|
Hi Asen, > I have gotten OpenC++ to work in a Visual Studio .NET 2003 solution. Oops, me too,I should have read the list before I started top evaluate opencxx... :-) > However I am still trying to figure out problems compiling the .mc metaclasses. I myself do it only statically now but to build and load a dll should not be problem too. > How do I submit changes that fix new MSVC specific things? > For example the new operator is defined as throw(...) and I have a fix for this. > (I don't know if that's new ANSI or just another Microsoft Specific stuff) That's MSVC specific. However, its STL is full of this, so opencxx must cope with it, if it wants to win MSVC customers :-) Standard: (no specification) The function can throw any exception. throw(type), throw(type1, type2), ... The function can throw an exception of type1, type2, ... throw() The function does not throw an exception. MSVC: (no specification) The function can throw any exception. throw(...) The function can throw any exception. throw(type), throw(type1, type2), ... The function can throw an exception of type1, type2, ... However, in Visual C++ .NET, this is interpreted as throw(...). throw() The function does not throw an exception. > Also there is a new type __w64 which has to be added as a keyword. Yep, and more, which I must have added. Currently I did it as Ignore but it is no the best way; I lost the information about the type... typedef __w64 unsigned int size_t; It makes better port to 64 bits in MSVC because it causes a special warning by such an assignment: size_t foo = ...; unsigned int bar = foo; // warning Ferda |