Oenone,
As Herfried suggests I would use a Nullable(Of DateTime) in .NET 2.0 to
represent a "null date" (or one of the other methods in .NET 1.x) rather
then a "special value".
| Public Sub DoSomething(Opt ional ByVal SomeDate As Date = Nothing)
| [...]
| End Sub
|
| (I believe this fails to compile in VB2003).
It fails to compile in VB 2003, which feels like a bug as this is allowed:
Dim empty As DateTime = Nothing
| Is this the intended documented behaviour of declaring the optional
| parameter in this way?
Maybe ;-)
Rather then use an optional parameter I would use an overloaded method.
Considering that Nullable(Of T) cannot be optional...
Public Sub DoSomething()
DoSomething(Not hing)
End Sub
Public Sub DoSomething(ByV al SomeDate As Nullable(Of Date))
End Sub
| Can I use this safe in the knowledge that the
| behaviour won't break or change in the next release of VB?
I would think you would be safe, As I stated I consider the error in .NET
1.x above to be a bug.
Nothing is defined (has always been defined) as the "default value" for a
type.
http://msdn2.microsoft.com/en-us/0x9tb07z(VS.80).aspx
For reference types this means a null reference. For value types it means
"all zeros" or False in the case of Boolean, For structures all its members
are set to their defaults. In the case of DateTime this happens to be
DateTime.MinVal ue.
For example try:
Dim empty As DateTime = Nothing
Dim minValue As DateTime = DateTime.MinVal ue
Debug.Assert(em pty = minValue)
--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
"Oenone" <oe****@nowhere .com> wrote in message
news:ub******** ******@TK2MSFTN GP04.phx.gbl...
| In our applications, we use the special value of DateTime.MinVal ue to
| represent "null dates" throughout all our code. We recently ran into an
| issue where we wanted an optional date parameter for a procedure. We
weren't
| able to declare it with DateTime.MinVal ue as its default value, as
MinValue
| is a read-only property rather than a constant. To work around, we had to
| use a "magic date" that we checked for later on. I was never very happy
with
| that solution.
|
| Today however I noticed that VB2005 is quite happy with the following:
|
| \\\
| Public Sub DoSomething(Opt ional ByVal SomeDate As Date = Nothing)
| [...]
| End Sub
| ///
|
| (I believe this fails to compile in VB2003).
|
| The value that is present in SomeDate if no date is provided by the
calling
| code is DateTime.MinVal ue (i.e., the default value for an uninitialised
date
| variable).
|
| Is this the intended documented behaviour of declaring the optional
| parameter in this way? Can I use this safe in the knowledge that the
| behaviour won't break or change in the next release of VB?
|
| Thanks,
|
| --
|
| (O)enone
|
|
