[Mono-bugs] [Bug 36376][Nor] Changed - mcs produces different output for enums than csc

[bugzilla-daemon@rocky.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 mathpup@mylinuxisp.com.

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

--- shadow/36376	Tue Jan  7 07:19:03 2003
+++ shadow/36376.tmp.18920	Sat Jan 11 18:46:52 2003
@@ -1,13 +1,13 @@
 Bug#: 36376
 Product: Mono/MCS
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: mathpup@mylinuxisp.com               
 QAContact: mono-bugs@ximian.com
@@ -93,6 +93,21 @@
 
 
 ------- Additional Comments From lupus@ximian.com  2003-01-07 07:19 -------
 The behaviour is fine according to our reading of the spec (and the
 behaviour of the ms runtime). The portable.net people should have
 fixed their loader to deal with it already.
+
+------- Additional Comments From mathpup@mylinuxisp.com  2003-01-11 18:46 -------
+I recently found additional information on enum declarations in Partition I, 
+Section 7.5.2, which I had not seen previously. According to CLS Rule 9, 
+"Literal static fields (see clause 7.6.1) of an enum shall have the type of the 
+enum itself." In the examples I posted originally, notice that the static literal 
+fields have type int32 and not the type of the enum itself, which would be 
+"valueType QFont/Weight". In light of this, I really think that this is a bug that 
+needs to be corrected. Although Microsoft's tools currently do not complain 
+about this output from mcs, it is conceivable that future versions might be 
+more strict about these declarations, so it seems reasonable to fix this 
+problem. And, of course, there is the issue that it's best to match csc's output 
+where possible. 
+ 
+