Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Unresolved parent class constructors in DLLs X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Date: Thu, 23 May 2002 07:20:04 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Jason Spence" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4MLLQp24988 > -----Original Message----- > From: Jason Spence [mailto:jspence@lightconsulting.com] > Sent: Thursday, May 23, 2002 5:20 AM > Can you even do stuff like this with PE DLLs? Yes. But you've got to resolve all symbols at link time. Dynamically registering classes aren't the proble here - the problem is your parent class needs to be available to the linker for the child (as you've stated in your title). My 2c: put the parent in a .dll of it's own, and link against that from the children and the program. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/