Re: Design: Custom Exception Usage
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Tue, 08 Apr 2008 08:29:12 -0700
On Tue, 08 Apr 2008 04:28:47 -0700, Anthony Jones <Ant@xxxxxxxxxxxxxxxx> wrote:
[...]Secondly, when you want to propogate any messages back to the calling
method, use OUT parameter from C# or use ByRef at VB.NET
That IMO isn't
My advice would be avoid OUT or ByRef parameter like the plague.
Hmmm...
While I'd agree that in this thread, the suggestion to use a by-reference parameter doesn't make much sense (exceptions are meant to be thrown :) ), I wouldn't say that the general technique should be avoided "like the plague". There are too many examples of situations in which a by-reference parameter is useful and not at all harmful for a broad generalization like that to be valid.
Pete
.
- Follow-Ups:
- Re: Design: Custom Exception Usage
- From: Anthony Jones
- Re: Design: Custom Exception Usage
- References:
- Design: Custom Exception Usage
- From: Terrence Jones
- Re: Design: Custom Exception Usage
- From: DSK Chakravarthy
- Re: Design: Custom Exception Usage
- From: Anthony Jones
- Design: Custom Exception Usage
- Prev by Date: Re: Creating a unit test in vs2008 for an object that holds strings?
- Next by Date: Problem occurs in loading managed C++ dll.
- Previous by thread: Re: Design: Custom Exception Usage
- Next by thread: Re: Design: Custom Exception Usage
- Index(es):
Loading