| Groups | Blog | Home |
dotnet general : Option Strict ON - WHY use it??
I have a project that was created all with Option Strict OFF. Works great,
not a problem with it. But if I turn Option Strict ON then I get a LOT of errors. My question, should I even care about Option Strict? What advantages do I get with Option Strict On? Does better type statement make my code run faster? If anyone knows THE ANSWERS! please fill me in. I have ideas and belief but I would once and for all like to know what the difference is. Thank in advance Clyde W.
Answers inline
[quoted text, click to view] "Microsoft News" wrote: > I have a project that was created all with Option Strict OFF. Works great, > not a problem with it. But if I turn Option Strict ON then I get a LOT of > errors. > > My question, should I even care about Option Strict? Becaue you don't like sloppy code. [quoted text, click to view] > What advantages do I get with Option Strict On? The primary one is forcing explicit coding standards. [quoted text, click to view] > Does better type statement make my code run faster? NO. But, Option Strict can get rid of some really annoying logic errors (syntax errors blow up, logic errors introduce bad data to application, possibly even messing up your database). OK, I will take that back. There are times when Option Strict can improve performance, as well, by taking away certain VB.NET crutches. [quoted text, click to view] > If anyone knows THE ANSWERS! please fill me in. I have ideas and belief but > I would once and for all like to know what the difference is. Overall, explicit coding is better, both for maintenance and ensuring your code runs as expected. In 90% + of scenarios, turing Option Strict OFF is fine. It is that small percent where it kills you. In most cases, bad programming practice causes code to blow up when you turn Option Strict ON. It is better to conquer those potential problems than leave them and turn it back OFF. This is much like treating WARNINGS as ERRORS. While code works fine when they are there, there is a small percentage of code that either bombs, or worse, corrupts data when WARNINGS are left in. Best to erradicate than take chances. Just my two cents. --- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA *************************** Think Outside the Box!
[quoted text, click to view]
With Deft Fingers, "Cowboy (Gregory A. Beamer) - MVP" wrote: >It is better to conquer those potential problems than leave them and turn it >back OFF. This is much like treating WARNINGS as ERRORS. While code works >fine when they are there, there is a small percentage of code that either >bombs, or worse, corrupts data when WARNINGS are left in. Best to erradicate >than take chances. Just my two cents. Interesting... I've too have always wondered about it. But my question (which really doesn't need to be answered) is "why then NOT have it as a 'default' ON and force all of us to clean UP our code? If we "had" to write better code, then we would... but if we are not 'forced' to... we write 'just to get by' code (and I am horribly guilty of that) (: Regards,
Kelly,
You have more answers including mine in the dotnet language.vb newsgroup. Please do not multipost. Cor
Bruce,
Probably it is not by default "on" because of the large part of VB6 programmers which are migrating, who will probably become crazy when they have to do the casting as well. I have it by default "on" in the Options and have seen not one situation where I have to set it to "of". However it is easier trying with option strict of, because sometimes you have to cast more times with option strict on. (By instance when you are trying something with MSHTML you can better start doing it with option strict of and set the casting than later and put option strict on) Just my thought, Cor
[quoted text, click to view] "Microsoft News" <Name@coxinet.net> wrote in message This is from the .net sdknews:ukLhAsH7EHA.3908@TK2MSFTNGP12.phx.gbl... > I have a project that was created all with Option Strict OFF. Works great, > not a problem with it. But if I turn Option Strict ON then I get a LOT of > errors. > > My question, should I even care about Option Strict? > What advantages do I get with Option Strict On? > Does better type statement make my code run faster? > > If anyone knows THE ANSWERS! please fill me in. I have ideas and belief but > I would once and for all like to know what the difference is. > > Thank in advance > > Clyde W. > > Visual Basic .NET generally allows implicit conversions of any data type to any other data type. Data loss can occur when the value of one data type is converted to a data type with less precision or smaller capacity, however, a run-time error message will occur if data will be lost in such a conversion. Option Strict ensures compile-time notification of these types of conversions so they may be avoided. Mike
[quoted text, click to view]
With Deft Fingers, "Cor Ligthert" <notmyfirstname@planet.nl> wrote: >I have it by default "on" in the Options and have seen not one situation >where I have to set it to "of". Huh! I didn't even see that in Options! I'll go look (kind of thought it was funny that you couldn't see it one way or the other). [quoted text, click to view] >have to cast more times with option strict on. (By instance when you are >trying something with MSHTML you can better start doing it with option >strict of and set the casting than later and put option strict on) Thanks Cor!
It should be on by default - that's one of the main things that people take
pot shots at VB.NET about -- W.G. Ryan, MVP www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com [quoted text, click to view] "Mr. B" <User@NoWhere.com> wrote in message news:lgq1t0to7e72jvstqpg2utp1j4bgsf5q9l@4ax.com... > With Deft Fingers, "Cowboy (Gregory A. Beamer) - MVP" wrote: > > >It is better to conquer those potential problems than leave them and turn it > >back OFF. This is much like treating WARNINGS as ERRORS. While code works > >fine when they are there, there is a small percentage of code that either > >bombs, or worse, corrupts data when WARNINGS are left in. Best to erradicate > >than take chances. Just my two cents. > > Interesting... I've too have always wondered about it. But my question (which > really doesn't need to be answered) is "why then NOT have it as a 'default' ON > and force all of us to clean UP our code? > > If we "had" to write better code, then we would... but if we are not 'forced' > to... we write 'just to get by' code (and I am horribly guilty of that) (: > > Regards, > > Bruce
The fact that you 'get all these errors' tells you that your code has
issues. Go check out the DailyWTF for proof. Almost all of the REALLY bad VB.NET code can only be as bad as it is b/c Option Strict is off Your code will run a lot faster with Option Strict on and you'll have a safety net to protect you from a lot of really bad but easy to make mistakes. Moreoever by using strong typing - you get intellisense support. Option Strict Off = Option Slow ON! -- W.G. Ryan, MVP www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com [quoted text, click to view] "Microsoft News" <Name@coxinet.net> wrote in message news:ukLhAsH7EHA.3908@TK2MSFTNGP12.phx.gbl... > I have a project that was created all with Option Strict OFF. Works great, > not a problem with it. But if I turn Option Strict ON then I get a LOT of > errors. > > My question, should I even care about Option Strict? > What advantages do I get with Option Strict On? > Does better type statement make my code run faster? > > If anyone knows THE ANSWERS! please fill me in. I have ideas and belief but > I would once and for all like to know what the difference is. > > Thank in advance > > Clyde W. > >
Greg:
Not trying to nitpick but There's a big performance issue with leaving option strict off. As Dan Appleman has pointed out - Option Strict Off = Option Slow On. -- W.G. Ryan, MVP www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com [quoted text, click to view] "Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@comcast.netNoSpamM> wrote in message news:4D173A5F-5A35-484B-A2A0-7FD55C08B1C2@microsoft.com... > Answers inline > > "Microsoft News" wrote: > > > I have a project that was created all with Option Strict OFF. Works great, > > not a problem with it. But if I turn Option Strict ON then I get a LOT of > > errors. > > > > My question, should I even care about Option Strict? > > Becaue you don't like sloppy code. > > > What advantages do I get with Option Strict On? > > The primary one is forcing explicit coding standards. > > > Does better type statement make my code run faster? > > NO. But, Option Strict can get rid of some really annoying logic errors > (syntax errors blow up, logic errors introduce bad data to application, > possibly even messing up your database). > > OK, I will take that back. There are times when Option Strict can improve > performance, as well, by taking away certain VB.NET crutches. > > > If anyone knows THE ANSWERS! please fill me in. I have ideas and belief but > > I would once and for all like to know what the difference is. > > Overall, explicit coding is better, both for maintenance and ensuring your > code runs as expected. In 90% + of scenarios, turing Option Strict OFF is > fine. It is that small percent where it kills you. In most cases, bad > programming practice causes code to blow up when you turn Option Strict ON. > It is better to conquer those potential problems than leave them and turn it > back OFF. This is much like treating WARNINGS as ERRORS. While code works > fine when they are there, there is a small percentage of code that either > bombs, or worse, corrupts data when WARNINGS are left in. Best to erradicate > than take chances. Just my two cents. > > > --- > > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > > *************************** > Think Outside the Box! > ***************************
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |