Tor Lillqvist 7323bc3405 WaE: warning C4100: 'aEvent' : unreferenced formal parameter ... I thought SAL_WARN_IF etc worked in such a way that any variables used in the condition would be "used" from the compiler's point of view, even in an optimising build case where SAL_DETAIL_ENABLE_LOG_WARN is false and SAL_WARN_IF should optimise away? Change-Id: I728e1eeb8559e1299abf403afceb0e2748d08857		2013-09-09 22:25:50 +03:00
..
autorecovery.cxx	Use SAL_INFO instead of framework's own WRITE_LOGFILE	2013-09-08 23:51:41 +03:00
ContextChangeEventMultiplexer.cxx
desktop.cxx	Bin some uses of the stupid DECLARE_ASCII macro	2013-09-09 00:58:15 +03:00
dispatchhelper.cxx
frame.cxx	WaE: warning C4100: 'aEvent' : unreferenced formal parameter	2013-09-09 22:25:50 +03:00
fwk_services.src
license.cxx	Bin unused remains of framework's own "debug framework"	2013-09-09 00:29:23 +03:00
mediatypedetectionhelper.cxx
modulemanager.cxx
pathsettings.cxx	Try to keep older(?) gcc versions happy	2013-09-09 01:42:07 +03:00
sessionlistener.cxx
substitutepathvars.cxx	Use SAL_WARN_IF instead of framework's home-grown LOG_ASSERT(2)	2013-09-08 23:51:41 +03:00
tabwindowservice.cxx	Use SAL_WARN_IF instead of framework's home-grown LOG_ASSERT(2)	2013-09-08 23:51:41 +03:00
taskcreatorsrv.cxx
uriabbreviation.cxx
urltransformer.cxx	Bin some uses of the stupid DECLARE_ASCII macro	2013-09-09 00:58:15 +03:00