Zooko wrote: > The only clean, long-term solution I can think of for the long term > is to change Crypto++ to remove definitions from header files so that > code like mine will get only undefined symbols by #include'ing Crypto+ > + header files. For example, if ConstByteArrayParameter were > declared as "class ConstByteArrayParameter;" in algparam.h and > defined only in some implementation file such as "algparam.cpp", then > the compiler and linked when building my ecdsa.so would know that it > didn't know the actual type of ConstByteArrayParameter and any RTTI > code would be compiled to use an indirect symbol that would not be > resolved until load time. Is that right?
I'm not sure I understand what you're suggesting. If algparam.h only contains "class ConstByteArrayParameter;", how do users call its members? Is this still a Mac specific problem, BTW? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
