linux-kernel - Re: macros: "do-while" versus "({ })" and a compile-time error

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 09 Jan 2007 21:19:17 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	"linux-os (Dick Johnson)" <linux-os@...logic.com>
CC:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: macros:  "do-while" versus "({ })" and a compile-time error

linux-os (Dick Johnson) wrote:
> On Tue, 9 Jan 2007, Stefan Richter wrote:
>> The limitations are certainly highly compiler-specific.
> 
> I don't think so.

I referred to the ({ expr; }) in this remark, not to do-while. It's not
a valid construct in many flavors of the C language in the first place.
Also, occurrences of ({ expr; }) could be expandable to a constant
expression but would still not be accepted by gcc's parser outside of
functions.
-- 
Stefan Richter
-=====-=-=== ---= -=--=
http://arcgraph.de/sr/
-
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/