23 Jun
2014
23 Jun
'14
8:49 a.m.
On Monday 23 June 2014 12:16:17 you wrote:
On Monday 23 June 2014 08:32:59 Adam Romanek wrote:
It turns out that GCC provides a way to silence such warnings selectively via a #pragma [3]. However, I'm not sure this is the right way to go.
Yes, but I'm hesitant to silence the warning since it may reveal the actual problems. I'll have to do that though if there's no other solution.
Unfortunately, a pragma doesn't work in my case - the warning is still generated even though I put the pragma before my code that triggers it. Wrapping boost::optional definition with it also doesn't work.