[Mono-bugs] [Bug 74974][Maj] New - "while breaking" problem new throw in condition statement

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ice-k at amnesty.scene.pl.

http://bugzilla.ximian.com/show_bug.cgi?id=74974

--- shadow/74974	2005-05-17 08:52:01.000000000 -0400
+++ shadow/74974.tmp.16352	2005-05-17 08:52:01.000000000 -0400
@@ -0,0 +1,66 @@
+Bug#: 74974
+Product: Mono: Compilers
+Version: 1.1
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: C#
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: ice-k at amnesty.scene.pl               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: "while breaking" problem  new throw  in condition statement
+
+When put 'throw new Exception' in 'if' scope condition 'break' in else 
+scope not break while loop
+
+---------------------- source ----------------------------------------
+                        int TestVal = 10;                          
+			
+                        switch( TestVal ) 
+                        {
+                                case 10:
+
+	                               	while( true )
+                                	{
+						if ( TestVal == 1 ) 
+						{
+							throw new 
+Exception ("Error Test");
+						}
+						else
+						{
+                                        	
+	break;                                          
+						}
+                                	}
+
+                                	TestVal = 20;
+                                break;
+                        }                               
+
+                        Console.WriteLine("Val-> " + 
+TestVal);                
+
+---------------------------------------------------------------------------
+
+
+
+Actual Results:
+Val->10
+
+Expected Results:
+Val->20
+
+How often does this happen?
+
+
+Additional Information:
+last mono 1.1.7
+the same result on 1.0.4
+when compiled by csc all is fine