[Mono-bugs] [Bug 47857][Wis] Changed - mono does not types to not have a super type

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 24 Aug 2003 17:14:41 -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 vargaz@freemail.hu.


--- shadow/47857	2003-08-24 17:11:28.000000000 -0400
+++ shadow/47857.tmp.3175	2003-08-24 17:14:41.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 47857
 Product: Mono/Runtime
 Version: unspecified
+OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: INVALID
+Severity: Unknown
 Priority: Wishlist
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: jackson@latitudegeo.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -46,6 +46,24 @@
 ------- Additional Comments From jackson@latitudegeo.com  2003-08-24 17:11 -------
 Created an attachment (id=5203)
 Proposed patch
+------- Additional Comments From vargaz@freemail.hu  2003-08-24 17:14 -------
+According to the ECMA spec, partition II, section 21.34:
+11.	With the sole exception of System.Object, for any Class, Extends
+shall index a valid row in the TypeDef or TypeRef table, where valid
+means 1 <= row <= rowcount.  In addition, that row itself shall be a
+Class (not an Interface or ValueType)  In addition, that base Class
+shall not be sealed (its Flags.Sealed shall be 0)  [ERROR]
+This means that the runtime is not required to support an extends 
+field with a 0 value. If you compile your testcase with MS ilasm, the 
+generated class will inherit from System.Object. So the problem is
+that our ilasm does not automatically make all such types inherit from