lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 01 Aug 2006 11:39:31 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Hua Zhong <hzhong@...il.com>
Cc:	'Jiri Slaby' <jirislaby@...il.com>,
	'Heiko Carstens' <heiko.carstens@...ibm.com>,
	'Andrew Morton' <akpm@...l.org>, linux-kernel@...r.kernel.org,
	'Martin Schwidefsky' <schwidefsky@...ibm.com>
Subject: RE: do { } while (0) question

On Tue, 2006-08-01 at 02:03 -0700, Hua Zhong wrote:
> > #if KILLER == 1
> > #define MACRO
> > #else
> > #define MACRO do { } while (0)
> > #endif
> > 
> > {
> > 	if (some_condition)
> > 		MACRO
> > 
> > 	if_this_is_not_called_you_loose_your_data();
> > }
> > 
> > How do you want to define KILLER, 0 or 1? I personally choose 0.
> 
> Really? Does it compile?

No, and that is the whole point.

The empty 'do {} while (0)' makes the missing semicolon a syntax error.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ