Scott McMillan (scott++at++ht.com)
Mon, 28 Oct 1996 12:04:04 -0500 (EST)
> If the class in question has a non-initialized const member variable and no
> default constructor defined the compiler apparently creates a default
> constructor that the linker is complaining about.
Note I only got this with the N32/64 versions of the linker (ld32 and ld64).
I have not tested under different configurations (like with the 7.0
compilers).
This warnings went away when I added a default constructor to the classes it
was complaining about (__TID_#x seems to be the "mangled" name for the default
constructor of class x). I made it empty and put it in the private section
where it could not be accessed.
Can a C++ guru explain this behaviour (the warnings, not the fact that I
didn't want a default constructor :-)?
scott
-- Scott McMillan | HT Medical, Inc. | Developing virtual environ- scott++at++ht.com | http://www.ht.com | ment medical and surgical Ph: 301-984-3706 | 6001 Montrose Rd., Ste. 902 | simulations and surgery Fax: 301-984-2104 | Rockville, MD 20852 | simulation creation tools.======================================================================= List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:49 PDT