On Wed, Jan 14, 2009 at 3:54 PM, Gevorg Voskanyan <v_gevorg@yahoo.com> wrote:
Robert Jones wrote:

[snip]

> Yes, that was the conclusion I came to, and in fact I can use the properties
> on a per file basis to do this. Strangley it also works if I put
> #pragma warning( disale : 4503 )
> at the top of the .cpp file causing problems, but does not work if I put

> #pragma warning( push )
> #pragma warning( disable : 4503 )
> ...my whole .cpp file
> #pragma warning( pop )

[snip]

> Thanks,
> Rob.

Just out of curiosity, why do you put #pragma warning( push/pop ) around your .cpp file's content? Do some other files #include your .cpp?


Good point, to which the answers are (a) Stupidity & (b) No, which means you have almost
solved my problem!

It would still seem reasonable to put push/pop around a single function tho', which also fails
to silence the warning.

Thanks very much.

Rob.