<jaddington@shaw.ca> wrote:

>I have a 3rd control that throws an exception if the syntax of a method call
>is incorrect. I am passing dynamic strings to that method so it is
>acceptable that the method will fail. I have my try...catch setup as
>
>try{ ...}
>catch(Control.StrangeException sEx){ }
>
>I get a compiler warning that I am not using sEx. I don't want to do
>anything if the method fails and I would like the warnings to go away... any
>ideas?
>
>thx
>
>jack
>

Jack Addington <jaddington@shaw.ca> wrote:
> I have a 3rd control that throws an exception if the syntax of a method call
> is incorrect. I am passing dynamic strings to that method so it is
> acceptable that the method will fail. I have my try...catch setup as
>
> try{ ...}
> catch(Control.StrangeException sEx){ }
>
> I get a compiler warning that I am not using sEx. I don't want to do
> anything if the method fails and I would like the warnings to go away... any
> ideas?

sadhu <senthilkumar@wdevs.com> wrote:
> It would have been nice if the compiler allowed the same thing for
> unused method parameters also. Like
> int SomeFunc(int x, int);

"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.1c8b87696c60857698bde6@msnews.microsoft.com...
> Jack Addington <jaddington@shaw.ca> wrote:
>> I have a 3rd control that throws an exception if the syntax of a method
>> call
>> is incorrect. I am passing dynamic strings to that method so it is
>> acceptable that the method will fail. I have my try...catch setup as
>>
>> try{ ...}
>> catch(Control.StrangeException sEx){ }
>>
>> I get a compiler warning that I am not using sEx. I don't want to do
>> anything if the method fails and I would like the warnings to go away...
>> any
>> ideas?
>
> Just don't include the variable:
>
> catch (Control.StrangeException) { }
>
> --
> Jon Skeet - <skeet@pobox.com>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too