cody wrote:

> System.Diagnostics.Debug.Assert();
>
> Hello??? A language should encourage programmers to heavily use the
> assert-feature, since it improves safety, stability, readability and
> maintainability of software. Most language designers recognized this, see
> C/C++ and Java which supports an assert keyword.
>
> My question now is, will C# support in future a single keyword for
> System.Diagnostics.Debug.Assert(), just like lock is a keyword for
> Monitor.Enter()?
>
> Putting "using System.Diagnostics.Debug;" in every single source file, is
> not acceptable for me.
> assert is/should be used in every application, no matter which kind of
> application it is. Name me just one method/class where this is also the
> case.
>
> What do you think?
>

> > System.Diagnostics.Debug.Assert();
> >
> > Hello??? A language should encourage programmers to heavily use the
> > assert-feature, since it improves safety, stability, readability and
> > maintainability of software. Most language designers recognized this,
see
> > C/C++ and Java which supports an assert keyword.
> >
> > My question now is, will C# support in future a single keyword for
> > System.Diagnostics.Debug.Assert(), just like lock is a keyword for
> > Monitor.Enter()?
> >
> > Putting "using System.Diagnostics.Debug;" in every single source file,
is
> > not acceptable for me.
> > assert is/should be used in every application, no matter which kind of
> > application it is. Name me just one method/class where this is also the
> > case.
> >
> > What do you think?
> >
>
> I agree that this probably would have been a good thing to have in
> version 1.0, but I doubt they'd add it as a keyword now.
>
> It would break some existing code,

> and the current usage of
> Debug.Assert() (in conjunction with a "using System.Diagnostics;")
> already does the job pretty much as well an "assert" keyword would so
> there's little added benefit.
>
> Note that the lock statement is more than just Monitor.Enter()... It
> encapsulates Monitor.Enter() followed by a try/finally block that
> ensures that Monitor.Exit() is called.