• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 263
  • Last Modified:

behavior of select case .net 2005

Hello,
Can someone explain to me why this select case statement does not have to evaluate all the conditions when I insert a breakpoint and step through it?
It will just jump right to the exact one it evaluates as true even if its the last one.

If I change the select statement to be something like this it will stop at each case expressionlist
case 10
   'do something
case 25
   'do something

Or if I change it to strings it will stop at each case expressionlist
A link would be great!

Dim x As Integer
     
      x = 25
      Select Case x
         Case 1 To 10
            Debug.Print(x)
         Case 11 To 20
            Debug.Print(x)
         Case 21 To 30
            Debug.Print(x)
         Case Else
            Debug.Print(x)
      End Select

Thank you!
0
mdiglio
Asked:
mdiglio
1 Solution
 
newyuppieCommented:
from:
http://msdn2.microsoft.com/en-us/library/cy37t14y.aspx

Remarks
If testexpression matches any Case expressionlist clause, the statements following that Case statement run up to the next Case, Case Else, or End Select statement. Control then passes to the statement following End Select. If testexpression matches an expressionlist clause in more than one Case clause, only the statements following the first match run.
...
Note  
A Case statement with multiple clauses can exhibit behavior known as short-circuiting. Visual Basic evaluates the clauses from left to right, and if one produces a match with testexpression, the remaining clauses are not evaluated. Short-circuiting can improve performance, but it can produce unexpected results if you are expecting every expression in expressionlist to be evaluated. For more information on short-circuiting, see Boolean Expressions.
 
0
 
mdiglioAuthor Commented:
Thanks for the reply.
I don't think this answers what I am after.
If it does answer it then I would need it explained

Why when I step through the above code ( pressing F8 ) do these expressionlists never get evaluated...case 1 to 10 | case 11 to 20
it just jumps to the one that evaluates as true...Case 21 To 30. How does it know?

If I remove the TO keyword it will stop at each line until it evaluates to true.


       
0
 
SanclerCommented:
My guess - and I stress it is no more than that - is that it is to do with the difference between value types (e.g. integers) and reference types (e.g. strings).  In part, that guess is because - unlike you report - whenever I have just tested with integers (whether single - e.g. Case 25 - or banded - e.g. Case 21 To 30) program flow jumps straight to the "right" answer, if there is one.  My thinking is that, with a value type, in effect the "answer is there in the question": but with reference types, the program has to look up the value that is to be compared, all it has is a reference to that value.

Roger
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
AlexFMCommented:
This is MSIL code produced by compiler for select case fragment:

.method public static void  Main() cil managed
{
  .entrypoint
  .custom instance void [mscorlib]System.STAThreadAttribute::.ctor() = ( 01 00 00 00 )
  // Code size       198 (0xc6)
  .maxstack  2
  .locals init ([0] int32 x,
           [1] int32 VB$t_i4$L0,
           [2] int32 VB$CG$t_i4$S0)
  IL_0000:  nop
  IL_0001:  ldc.i4.s   25
  IL_0003:  stloc.0
  IL_0004:  nop
  IL_0005:  ldloc.0
  IL_0006:  ldc.i4.1
  IL_0007:  sub
  IL_0008:  stloc.2
  IL_0009:  ldloc.2
  IL_000a:  switch     (
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0089,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_0098,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7,
                        IL_00a7)
  IL_0087:  br.s       IL_00b6
  IL_0089:  nop
  IL_008a:  ldloc.0
  IL_008b:  call       string [Microsoft.VisualBasic]Microsoft.VisualBasic.CompilerServices.Conversions::ToString(int32)
  IL_0090:  call       void [System]System.Diagnostics.Debug::Print(string)
  IL_0095:  nop
  IL_0096:  br.s       IL_00c3
  IL_0098:  nop
  IL_0099:  ldloc.0
  IL_009a:  call       string [Microsoft.VisualBasic]Microsoft.VisualBasic.CompilerServices.Conversions::ToString(int32)
  IL_009f:  call       void [System]System.Diagnostics.Debug::Print(string)
  IL_00a4:  nop
  IL_00a5:  br.s       IL_00c3
  IL_00a7:  nop
  IL_00a8:  ldloc.0
  IL_00a9:  call       string [Microsoft.VisualBasic]Microsoft.VisualBasic.CompilerServices.Conversions::ToString(int32)
  IL_00ae:  call       void [System]System.Diagnostics.Debug::Print(string)
  IL_00b3:  nop
  IL_00b4:  br.s       IL_00c3
  IL_00b6:  nop
  IL_00b7:  ldloc.0
  IL_00b8:  call       string [Microsoft.VisualBasic]Microsoft.VisualBasic.CompilerServices.Conversions::ToString(int32)
  IL_00bd:  call       void [System]System.Diagnostics.Debug::Print(string)
  IL_00c2:  nop
  IL_00c3:  nop
  IL_00c4:  nop
  IL_00c5:  ret
} // end of method Module1::Main

VB Select Case is converted to MSIL switch statement. switch contains offsets for every number from 1 to 30. You can read more about MSIL switch statement here:
http://msdn2.microsoft.com/en-US/library/system.reflection.emit.opcodes.switch.aspx

Actually, it is executed by comparing x variable with numbers 1, 2, 3 ... 30. Since there is no exact match between produced MSIL code and VB code, debugger jumps directly to case line which meets the condition.
This is usual Assembly situation: there is exact way to convert VB code to MSIL, but it is impossible sometimes to reproduce VB code from MSIL.
0
 
mdiglioAuthor Commented:
Thanks to everyone for your responses
0
 
mdiglioAuthor Commented:
AlexFM ,
Is there an easy way for you to explain how you got the above code.
Or should that be asked as another question?
0
 
AlexFMCommented:
Run Microsoft IldAsm program:
Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\ildasm.exe
and open .NET Assembly (.exe or .Dll). Read more about ILDASM and MSIL if you are interesting in .NET internals.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now