U++ framework: U++ Developers corner » WARNINGS: LOG -> empty statement in RELEASE

Home » Developing U++ » U++ Developers corner » WARNINGS: LOG -> empty statement in RELEASE

Thu, 31 March 2011 09:29

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

dolik.rce wrote on Wed, 30 March 2011 16:18

mirek wrote on Wed, 30 March 2011 21:43

Are you sure that GCC guys will not warn about "empty block" someday? Smile

If they do, we can make it "#define LOG(X) {int i=0;}", so later they can start warning us about "useless code block" Very Happy

Then I would really start to consider using -Wno-empty-body (or -Wno-useless-code Smile

).

Honza

This one would yield "unused variable" even today... Smile

I guess the one possible way around would be:

inline void Nop() {}

#define LOG(x) Nop()

Mirek

		WARNINGS: LOG -> empty statement in RELEASE By: kohait00 on Wed, 30 March 2011 11:09
		Re: WARNINGS: LOG -> empty statement in RELEASE By: dolik.rce on Wed, 30 March 2011 13:14
		Re: WARNINGS: LOG -> empty statement in RELEASE By: kohait00 on Wed, 30 March 2011 14:01
		Re: WARNINGS: LOG -> empty statement in RELEASE By: mirek on Wed, 30 March 2011 21:43
		Re: WARNINGS: LOG -> empty statement in RELEASE By: dolik.rce on Wed, 30 March 2011 22:18
		Re: WARNINGS: LOG -> empty statement in RELEASE By: mirek on Thu, 31 March 2011 09:29
		Re: WARNINGS: LOG -> empty statement in RELEASE By: kohait00 on Thu, 31 March 2011 10:25
		Re: WARNINGS: LOG -> empty statement in RELEASE By: kohait00 on Tue, 05 April 2011 20:47
		Re: WARNINGS: LOG -> empty statement in RELEASE By: mirek on Thu, 07 April 2011 10:52

Previous Topic:	svn: patches, sandbox
Next Topic:	FEAT: Tcl as a plugin

Goto Forum:

] [

]

Current Time: Thu Sep 10 14:05:43 GMT+2 2026

Total time taken to generate the page: 0.01029 seconds