Hi Anthony,
I just tested the follow. It may be a good compromise for you. Add
#pragma warning( disable: 4100 ) to StdAfx.h.
Jeff
[EMAIL PROTECTED] wrote:
Im getting lots of "unreferenced formal parameters" warnings using
version 5.4 and visual studio 2005.
these are easy to get rid of by changing the function implementation to
not name the parameter...
change something like:
bool GetVoidValue(const char *name, const std::type_info &valueType,
void *pValue) const {return false;}
to:
bool GetVoidValue(const char *const std::type_info &void *const
{return false;}
I know this works for Visual Studio, not sure about other compilers.
You could also wrap the parameters in the function with a macro that
expands to something that will be optimized away. I know ive seen
other third party libraries do this.
This is a pretty minor issue, but when i see 180+ warnings (im using
warning level 4), its hard to sort out warnings from my code, and
warnings from third party stuff
-Anthony
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Crypto++
Users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cryptopp-users?hl=en
-~----------~----~----~----~------~----~------~--~---
