Debug.Assert

[Peter Morris]

In Delphi I used to use Assert as a development aid. During debug it would
ensure that certain conditions were met but in the Release build the Asserts
were not compiled into the application. I am assuming this is the same with
..NET too? Debug.Assert isn't compiled into a Release build?

The other thing I am curious about is this

public void DoSomething(Per son p)
{
if (p == null)
throw new ArgumentNullExc eption("P");
....
}

Why do people tend to use exceptions such as ArgumentNullExc eption instead
of something like this which I presume gets skipped in Release build and is
also quicker to type?

public void DoSomething(Per son p)
{
Debug.Assert(p != null, "P is null");
....
}

Pete

[Alun Harford]

Jon Skeet [C# MVP] wrote:

On Aug 1, 2:00 pm, Marc Gravell <marc.grav...@g mail.comwrote:

>I know it has been discussed before, but a language tweak would be very
welcome here; something like:

public void DoSomething(Per son !p) {...}

And let the compiler worry about it.

(although perhaps more meaningful syntax)

I'd go for "Person! person" to mirror "int? value".

This is exactly what Spec# uses. I *really* want that in C# 4 (or a C#3
version of Spec#)

Alun Harford