Jesse,
The code you show below (and anything else like it) is a bug.
In some cases it's used on purpose (mainly around the crypto providers)
to make sure someone isn't using multiple providers on us for times when
a provider is relying on a class within the same provider. However I've
thought f
None of my company's code currently relies on real-time type information
(RTTI), so we disable it to avoid the overhead. This is possible in
part because Xerces-C explicitly does not use RTTI (to ensure
portability). XML-Security-C, on the other hand, uses dynamic_cast<>
and thus relies on RTTI.
