try/catch compilation warning

[ChrisB]

Hello:

I notice that the following statements generate a "the variable 'e' is
declared but never used" warning:

try
{
Company.Fetch(CompanyID);
}
catch(RecordNotFoundException e)
{
return null;
}

I have no reason to use the variable e within my catch block and find this
warning annoying (my code is generating many such warnings). Is there a
commonly used way to avoid a compilation warning in this situation?

Thanks,
Chris

[Uri Dor]

catch(RecordNotFoundException)

ChrisB wrote:

Hello:

I notice that the following statements generate a "the variable 'e' is
declared but never used" warning:

try
{
Company.Fetch(CompanyID);
}
catch(RecordNotFoundException e)
{
return null;
}

I have no reason to use the variable e within my catch block and find this
warning annoying (my code is generating many such warnings). Is there a
commonly used way to avoid a compilation warning in this situation?

Thanks,
Chris

[Morten Wennevik]

Hi ChrisB,

Sure is, change your catch block to

catch
{
return null;
}

Happy coding!
Morten Wennevik [C# MVP]

[C# Learner]

ChrisB wrote:

[...]
I have no reason to use the variable e within my catch block and find this
warning annoying (my code is generating many such warnings). Is there a
commonly used way to avoid a compilation warning in this situation?

In that case, use the following to simply filter the exception.

try
{
Company.Fetch(CompanyID);
}
catch(RecordNotFoundException)
{
return null;
}

[Jon Skeet [C# MVP]]

ChrisB <pl****************@thanks.com> wrote:

I notice that the following statements generate a "the variable 'e' is
declared but never used" warning:

try
{
Company.Fetch(CompanyID);
}
catch(RecordNotFoundException e)
{
return null;
}

I have no reason to use the variable e within my catch block and find this
warning annoying (my code is generating many such warnings). Is there a
commonly used way to avoid a compilation warning in this situation?

Yes - don't declare the variable:

catch (RecordNotFoundException)
{
return null;
}

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Morten Wennevik <Mo************@hotmail.com> wrote:

Sure is, change your catch block to

catch
{
return null;
}

That then catches *all* exceptions, however, which may very well not be
what is wanted.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[ChrisB]

Simple enough. Thanks!

"C# Learner" <cs****@learner.here> wrote in message
news:Ou*************@TK2MSFTNGP10.phx.gbl...

ChrisB wrote:

[...]
I have no reason to use the variable e within my catch block and find this warning annoying (my code is generating many such warnings). Is there a
commonly used way to avoid a compilation warning in this situation?

In that case, use the following to simply filter the exception.

try
{
Company.Fetch(CompanyID);
}
catch(RecordNotFoundException)
{
return null;
}

[Morten Wennevik]

Good point

Happy coding!
Morten Wennevik [C# MVP]