It's not ambiguous, but it's also not self-evident; I've known programmers that didn't recognize it. Q_UNUSED offers the hint that it probably has something to do with being, well, UNUSED.

If I were building it from scratch, I'd probably encourage the use of it but we have a ton of code that doesn't look very QT-ish (and only marginly even C++-ish), so that's not a very interesting battle.  I just threw it out in the name of options.
On Sun Oct 06 2013 at 4:18:20 PM, Conrad Meyer <> wrote:
Is (void)foo; ambiguous? It takes a few less characters, isn't
surprising to people unfamiliar with Qt (like me ;-)), and only has
one meaning (that I'm aware of). It's probably more surprising if you
haven't seen it before, but...


On Sun, Oct 6, 2013 at 5:15 PM, Robert Lipe <> wrote:
> Thanx.  Applied.
> There's also the Q_UNUSED() macro available in our toolbox.  Some people
> find it more self-documenting than the (void)foo; but on a code base this
> size which already has many deep non-QT-isme, it may be a distraction.
> On Sun Oct 06 2013 at 10:07:12 AM, Conrad Meyer <> wrote:
>> For mapsource I left some unused parameters named, because the
>> proposed use (mps_ver) didn't seem readily inferable from the type
>> (int). For others (rte) I just removed the name when params were
>> unused.
>> Thanks,
>> Conrad
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
>> from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> Gpsbabel-code mailing list