Den 26-04-2012 15:41, Robert Story skrev: > An IRC user reports an issue with net-snmp-config.h: > > "when building against net-snmp, i have to modify net-snmp-config.h to #define > HAVE_DMALLOC_H 0, otherwise net-snmp-includes.h fails saying HAVE_DMALLOC_H > is not defined" > > This change was made in commit 3a423609cafaca7b729873295bcac3bf6cfb2bda, in > 2002. > > -#ifdef HAVE_DMALLOC_H > +#if HAVE_DMALLOC_H > > I thought that, since this macro comes from a configure check, that it is only > defined when true, and would be undefined instead of having a 0 value. > > There are several other defines in this file that were also changed to > "#if"... Is there a good reason no to use "#ifdef"?
But I gather this holds for all other HAVE_xxx symbols too, and they seem not to cause any problems? We use #if HAVE_xxx almost exclusively in the source. What compiler is that, who complains about this. And the change was in 2002, so it can't be that serious :-) But in principle, of course, it would be more correct to use #ifdef /Niels -- Niels Baggesen - @home - Århus - Denmark - n...@users.sourceforge.net The purpose of computing is insight, not numbers --- R W Hamming ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
