Comments on: VB.NET boolean operators and short-circuit evaluation http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/ Rails, Firefox, Anime, Mac Sat, 04 Feb 2012 15:38:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: dean http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-513648 dean Wed, 27 Feb 2008 10:14:08 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-513648 its annoying, but the reason is an old one. historically logical operators in vb are also used for bitwise expressions - they should have broken this when creating vb.net, but i guess they were worried about code conversions its annoying, but the reason is an old one. historically logical operators in vb are also used for bitwise expressions – they should have broken this when creating vb.net, but i guess they were worried about code conversions

]]> By: David Tan http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-395380 David Tan Mon, 17 Dec 2007 01:06:23 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-395380 You are definately not the first to find this a bit bizarre. Having no VB background and coming from other language makes this AndAlso / OrElse sounds a bit clumsy, and funny :) You are definately not the first to find this a bit bizarre. Having no VB background and coming from other language makes this AndAlso / OrElse sounds a bit clumsy, and funny :)

]]> By: Dot Net Books http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-152502 Dot Net Books Sun, 15 Apr 2007 13:44:37 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-152502 Since most developers using VB.NET used earlier versions of VB, and most new developers will probably use C#, doesn't it make sense to leave the way it operates? Since most developers using VB.NET used earlier versions of VB, and most new developers will probably use C#, doesn’t it make sense to leave the way it operates?

]]> By: sonali http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-140503 sonali Mon, 26 Mar 2007 12:43:14 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-140503 i want to write a code in VB.NEt in 2003 that will sync my outlook events & contacts list to my application. Kindly Suggest various solution for the same.. thanx i want to write a code in VB.NEt in 2003 that will sync my outlook events & contacts list to my application.

Kindly Suggest various solution for the same..

thanx

]]> By: Danny http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-59385 Danny Tue, 07 Nov 2006 18:52:35 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-59385 VB.NET's non-short circuit boolean expresssions hark back partly to when user defined functions were starting to be used. If you have a boolean expression that short circuits and its made up of functions then "if boolfooa() or boolfoob() then ...." wont eval boolfoob() if boolfooa() returns true. I think (?) thats the main use. VB.NET’s non-short circuit boolean expresssions hark back partly to when user defined functions were starting to be used. If you have a boolean expression that short circuits and its made up of functions then

“if boolfooa() or boolfoob() then
….”

wont eval boolfoob() if boolfooa() returns true. I think (?) thats the main use.

]]> By: Dennis Pallett http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1953 Dennis Pallett Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1953 I haven't got a clue why they designed it like this. I do know that I'm really enjoying PHP and its short-circuit evaluation though! :) I haven’t got a clue why they designed it like this. I do know that I’m really enjoying PHP and its short-circuit evaluation though! :)

]]> By: Chadom http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1954 Chadom Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1954 Agree with Dennis. In VBscript/ASP when get a value from data base, need two lines to test if it is a "valid" value : if (not isnull(foo)) and foo>"" then ... will crash if foo is null (second part is eval and null can't be compare with a string). Very ugly. Agree with Dennis. In VBscript/ASP when get a value from data base, need two lines to test if it is a “valid” value :
if (not isnull(foo)) and foo>”" then
…
will crash if foo is null (second part is eval and null can’t be compare with a string). Very ugly.

]]> By: Cheah Chu Yeow http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1952 Cheah Chu Yeow Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1952 Well, I can't say we are forced to use VB.NET - I have a feeling the lecturer would be open to using C#. He has even allowed the use of Flash for the GUI project we're doing. Well, I can’t say we are forced to use VB.NET – I have a feeling the lecturer would be open to using C#. He has even allowed the use of Flash for the GUI project we’re doing.

]]> By: Stephan Segraves http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1951 Stephan Segraves Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1951 Wait, isn't the whole point of .NET to allow the programmer to choose what language he wants to work with and be able to make group projects using that language? Kind of seems like your instructor is killing that idea... Wait, isn’t the whole point of .NET to allow the programmer to choose what language he wants to work with and be able to make group projects using that language? Kind of seems like your instructor is killing that idea…

]]> By: Vinnie http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1950 Vinnie Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1950 You'd pick up on C# fast; it's a lot like Java, just with a different framework attached to it. I wouldn't use it on your current project since everyone else would have no idea what's going on in your code, but something to keep in mind in the future. You’d pick up on C# fast; it’s a lot like Java, just with a different framework attached to it. I wouldn’t use it on your current project since everyone else would have no idea what’s going on in your code, but something to keep in mind in the future.

]]> By: Cheah Chu Yeow http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1949 Cheah Chu Yeow Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1949 <strong>Vinnie</strong>: Good idea why didn't I think of that earlier - now I'm far too committed to VB.NET because all the labs have been in VB.NET and I don't really want to spend time on picking up C# (though it shouldn't be too hard, I think). Besides, everyone else is using VB.NET and there's a group project going. <strong>Dennis</strong>: <em>Slightly</em> annoying? I think that is very annoying! You wouldn't happen to know why VB was designed this way, would you? Vinnie: Good idea why didn’t I think of that earlier – now I’m far too committed to VB.NET because all the labs have been in VB.NET and I don’t really want to spend time on picking up C# (though it shouldn’t be too hard, I think). Besides, everyone else is using VB.NET and there’s a group project going.

Dennis: Slightly annoying? I think that is very annoying! You wouldn’t happen to know why VB was designed this way, would you?

]]> By: Dennis Pallett http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1948 Dennis Pallett Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1948 I wish VBScript/ASP had OrElse and AndElse. It's slightly annoying to do: If IsEmpty(Request.QueryString("id")) = False Then If IsNumeric(Request.QueryString("id")) = True Then 'The id is valid Else 'The id is not empty, but not numeric End If Else 'The id is empty End If Instead of being able to do: If IsEmpty(Request.QueryString("id")) = False And IsNumeric(Request.QueryString("id")) = True Then 'The id is valid Else 'The id is either empty or not numeric End If (The second method would give an error of id contained letters) I wish VBScript/ASP had OrElse and AndElse.

It’s slightly annoying to do:
If IsEmpty(Request.QueryString(“id”)) = False Then
If IsNumeric(Request.QueryString(“id”)) = True Then
‘The id is valid
Else
‘The id is not empty, but not numeric
End If
Else
‘The id is empty
End If

Instead of being able to do:
If IsEmpty(Request.QueryString(“id”)) = False And IsNumeric(Request.QueryString(“id”)) = True Then
‘The id is valid
Else
‘The id is either empty or not numeric
End If

(The second method would give an error of id contained letters)

]]> By: Vinnie http://blog.codefront.net/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/comment-page-1/#comment-1947 Vinnie Wed, 30 Nov -0001 00:00:00 +0000 http://blog.codefront.net/archives/2004/01/25/vbnet-boolean-operators-and-short-circuit-evaluation/#comment-1947 Now why won't your teachers just let you use C#? ;) In any case, I think Or is still around because that's all that VB6 and earlier developers had. OrElse was just added in for VB.NET, and VB still has a lot of backward-compatible syntax that isn't necessary with the .NET framework. Now why won’t your teachers just let you use C#? ;)

In any case, I think Or is still around because that’s all that VB6 and earlier developers had. OrElse was just added in for VB.NET, and VB still has a lot of backward-compatible syntax that isn’t necessary with the .NET framework.

]]>