Hi Brandon, I do not understand your point. A class using MFcs cannot be a platform neutral class. What do you mean by "as soon as it catches wind of T-anything it blows up" If your intention is to do I/O with one of your class deriving/having,etc a MFC class inside, you can derive your class from TObject, add a ClassDef macro in the .h file and a ClassImp in the implementation file. You have to run rootcint on this class (these classes). rootcint may have difficulties with several MFC classes that are full of macros calling other macros. A possible solution is to embed the MFC includes between #ifndef __CINT__ MFC statements #endif Rene Brun Brandon Kohn wrote: >Hi guys, >Quick question, is there anyway that you could serialize a platform neutral class >without losing that platform neutrality? I'm working with an application that >makes use of MFC for parts of its operation, and as soon as it catches wind of >T-anything it blows up. I would like to use TObject wrappers for these classes, >but rootcint seems to complain about including these objects. Has any work been >done on this type of problem? I suppose what I'm asking is if root can serialize >non TObject derived classes who don't know what a TBuffer is.
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:51:03 MET