Hi Jeffrey, automatically generated copy ctor's won't compile if, for example, one of the contained objects (in your case the ofstream) has a private/protected copy ctor. Two ways to solve it: - provide a copy ctor for your class that is dummy or does something useful (whatever you like). Now rootcint will not generate one and the dictionary will compile fine. - don't contain objects but use a pointer to an object Cheers, Fons. > Hi root-sters! > > I'm not sure if this is exactly the right venue for this question, but I'm > sure someone here will know what I'm talking about. > > I am quite unfamiliar with CINT, and have been having some problems with > rootcint's automatic code generation. For example, when I include an > ofstream object as a data member in a class the automatically generated > copy constructor won't compile. My question is 1) is there a way to turn > off the automatic code generation when I run into problems, and 2) is > there a list of guidelines for what it can and can't handle so I can try > to avoid writing code that will cause it to fail. > > Thanks > > --------------------------------------------------------------------- > Jeffrey G Reid | jgreid@u.washington.edu | UW Nuclear Physics Lab > ===================================================================== > -- Org: CERN, European Laboratory for Particle Physics. Mail: 1211 Geneve 23, Switzerland E-Mail: Fons.Rademakers@cern.ch Phone: +41 22 7679248 WWW: http://root.cern.ch/~rdm/ Fax: +41 22 7677910
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:36 MET