[Mono-bugs] [Bug 41776][Min] Changed - Definite assignment problem

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Sun, 18 May 2003 17:17:02 -0400 (EDT)

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 martin@ximian.com.


--- shadow/41776	Tue May  6 12:23:27 2003
+++ shadow/41776.tmp.20134	Sun May 18 17:17:01 2003
@@ -1,13 +1,13 @@
 Bug#: 41776
 Product: Mono/MCS
 Version: unspecified
 OS: Red Hat 7.2
 OS Details: 
-Status: ASSIGNED   
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Minor
 Component: Misc
 AssignedTo: martin@ximian.com                            
 ReportedBy: staerk@inf.ethz.ch               
 QAContact: mono-bugs@ximian.com
@@ -45,6 +45,21 @@
 // Microsoft .NET
 // > csc Test3.cs
 // Test3.cs(7,7): warning CS0162: Unreachable code detected
 // > Test3.exe
 // 0
+------- Additional Comments From martin@ximian.com  2003-05-18 17:17 -------
+One could argue whether this is a bug or not.
+My decision not to fix this bug was based on the following:
+a) I think we should treat definity assignment errors just like
+   ordinary syntax errors and you can't have any syntax errors
+   in unreachable code.
+b) I don't see any reason why anyone should ever want to write
+   such code, so MCS's current behaviour of rejecting it doesn't
+   hurt anyone.
+c) If MS ever changes csc's behavior and makes it disallow definite
+   assignment errors in unreachable code, people will already have
+   their code bug-free because MCS is already enforcing it.