20 May
2014
20 May
'14
12:28 a.m.
On May 19, 2014 11:26:49 AM EDT, Adam Wulkiewicz
Then probably also
boost::ignore_unused_variable(v1) ; boost::ignore_unused_variables(v1, v2, v3);
for consistency.
Actually, I'd favor ignore_unused(). I see no reason for "variable" to be in the name. If you use a macro, then you'd need to distinguish between TYPEDEFs and VARIABLEs.
Or would putting it in boost::utility/BOOST_UTILITY be a better idea?
Glen's argument against config makes sense. Utility doesn't seem unreasonable. ___ Rob (Sent from my portable computation engine)