This is the only one that makes sense, although it wasn't meant to end up in this pull request. I couldn't take it out.

The reason for this is that when I compiled out of Code::Blocks (e.g., no fancy make magic), and I enabled memory leak warnings, I got a warning from my compiler, which is set to treat warnings as errors.

Beacuse when the conditional code further down is not compiled, then these variables end up unused.

We can discuss this one; it wasn't meant to be in this pull request.


Arnd R. Strube
Software-Architect

Windhoff Software Services GmbH
Hofstraße 17, 48712 Gescher
Tel.: +49 (0) 25 42 / 95 59 44 | Fax: +49 (0) 25 42 / 95 59 20
a.strube@wind-soft.de | http://www.wind-soft.de



SAP BI – Aktuelle Themen in unserem Webcast
Kurz, prägnant und kostenlos | Gleich anmelden!

Standorte: Amberg | Berlin | Hamburg | Ingolstadt | Stuttgart | Wiesbaden | Wolfsburg

Geschäftsführung: Jürgen Kemp, Norbert Sundermann, Carsten Reinecke, Markus Brünen
Gesellschaftssitz: Gescher
Handelsregister: HRB 4486, 48651 Coesfeld



________________________________________
From: Bas Vodde [notifications@github.com]
Sent: Tuesday, June 18, 2013 02:03
To: cpputest/cpputest
Cc: Arnd Strube
Subject: Re: [cpputest] withParameter() separate overload / override (#123)

In tests/TestHarness_cTest.cpp:

>       MemoryLeakDetector* memLeakDetector = MemoryLeakWarningPlugin::getGlobalDetector();
>       int memLeaks = memLeakDetector->totalMemoryLeaks(mem_leak_period_checking);
> +#endif
>       void* mem1 = malloc(10);


Why was this added?

—
Reply to this email directly or view it on GitHub<https://github.com/cpputest/cpputest/pull/123/files#r4738526>.