From: Grzegorz J. <ja...@he...> - 2004-04-19 08:45:15
|
Hi, On Fri, 16 Apr 2004, Ferdinand Prantl wrote: > > > Also mind you that typeinfo.h is a header file included in .NET 2003 > > so at some point <typeinfo> is being included which includes <typeinfo.h> > > but if you have the includes set to the occ folder it will include the > wrong one. > > I renamed typeinfo.h to type_info.h on mine. I think it might be worth > changing it > > altogether in the repository. AFAIK this was discussed here already along with solution that does not require renaming. In the latest version in sandbox_jakacki_frontend1 (to be merged to MAIN soon) each class has its own file, so class TypeInfo has its file TypeInfo.h; we cannot rename this file without breaking a rule, that the file name is constructed from class name. We cannot rename class without breaking backward compatibility. So that's why I don't like renaming. > The other solution, which I did is not to put the directory with opencxx > headers inti the include path. > > .../opencxx-2.7/src/... (you know this, here are the sources) > .../opencxx-2.7/include/opencxx/... (I copied the published and externally > used headers) > > Then only .../opencxx-2.7/include to path and: > > #include <opencxx/typeinfo.h> This will break if you are building new version of OpenC++, but have the old one installed in directory, that is early in include path (e.g. if you installed in /usr/local), as this directive will pull in the old header. Also remember about issues when building with srcdir!=builddir (I am not sure if they hit here, I have no time to analyze it at the moment, sorry.) The solution I used in sandbox_jakacki_frontend1 is: #include "../opencxx/typeinfo.h" BR Grzegorz > It is actually better way how to do includes, which is also more used in OSS > world. But no big problem with renaming, indeed. > > F. > > > _____________________________________________ > From: Ferdinand Prantl > Sent: Friday, April 16, 2004 13:01 > To: ope...@li... > Subject: RE: OpenC++ for .NET 2003 > > 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 > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Opencxx-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opencxx-users > > ################################################################## # Grzegorz Jakacki Huada Electronic Design # # Senior Engineer, CAD Dept. 1 Gaojiayuan, Chaoyang # # tel. +86-10-64365577 x2074 Beijing 100015, China # # Copyright (C) 2004 Grzegorz Jakacki, HED. All Rights Reserved. # ################################################################## |