Re: c++: dynamic_cast woes

## Dimitry Andric (dim@FreeBSD.org):

> Yes, this is a typical problem when type info is replicated across
> dynamic library boundaries. The best thing to prevent this is to
> ensure that the key functions for a class (typically constructors
> and destructors) are only in one translation unit (object file),
> and that object file is only in one .so file.

As FreeBSD is basically unsupported from upstream, this sounds
like I'm in for quite a bit of fun here. Well.

Thanks anyways,
Christoph

-- 
Spare Space