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

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

Wed, 30 March 2011 21:43

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

dolik.rce wrote on Wed, 30 March 2011 07:14

Hi kohait,

There is lot more warnings like this all over U++ Smile

IMHO better solution (more general and future-proof) would be defining LOG as nonempty macro:

#ifndef flagDEBUG
#define LOG(X) {}
#endif

I don't recall where the LOG is originally defined, but I'm sure you can find it Wink

Honza

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

		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: Wed Jul 01 08:30:11 GMT+2 2026

Total time taken to generate the page: 0.00603 seconds