Re: Option Strict
From: Steve C. Orr [MVP, MCSD] (Steve_at_Orr.net)
Date: 10/14/04
- Next message: NathanV: "Suggestions for implementing personalization"
- Previous message: NathanV: "Forms Authentication across directories"
- In reply to: Simon Harris: "Option Strict"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 13 Oct 2004 17:04:46 -0700
The most important thing is that it turns potential runtime errors into
compile time errors.
Compile time errors are much easier and less expensive to fix, and they'll
never reach your users.
-- I hope this helps, Steve C. Orr, MCSD, MVP http://Steve.Orr.net "Simon Harris" <too-much-spam@makes-you-fat.com> wrote in message news:uxdp6OWsEHA.2808@TK2MSFTNGP14.phx.gbl... > Hi All, > > I've been advised to use option strict. I've tried to read up on this, all > i can find is that it... > > "disallows implicit narrowing conversions" > > This kinda makes sense - Means I have to explicitly cast or convert data > when comparing/setting two different data types right? > > Is there any more to it than this? What are the benefits of using option > strict? > > Regards, > Simon. >
- Next message: NathanV: "Suggestions for implementing personalization"
- Previous message: NathanV: "Forms Authentication across directories"
- In reply to: Simon Harris: "Option Strict"
- Messages sorted by: [ date ] [ thread ]