>> Recently, we upgraded compilers and we're seeing a lot of >> warnings about "dereferencing type-punned pointer will break >> strict-aliasing rules" > > Well, the warning is technically correct. > The memdup call *does* re-cast these pointers in a potentially > non-safe manner. But memdup is working with raw memory, > so this isn't really a problem.
Probably. > I suppose you could consider tweaking the call to use 'void' rather > than 'char' pointers. In retrospect, that would have been a better > choice, and might keep your compiler happy. But note that this > change would have to be applied throughout the whole codebase. I'm running up against a local rule that requires our code to compile without warnings. I can ask for an exception for the generated code but maybe I'll do the void -> char change locally; I can't practically *re*generate the code so I'm not losing any thing. > ... ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
