[Mono-bugs] [Bug 73046][Nor] Changed - mcs/gmcs doesn't support new SecurityAction defined in 2.0
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 28 Feb 2005 03:32:12 -0500 (EST)
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 rharinath@novell.com.
http://bugzilla.ximian.com/show_bug.cgi?id=73046
--- shadow/73046 2005-02-25 18:03:15.000000000 -0500
+++ shadow/73046.tmp.10847 2005-02-28 03:32:12.000000000 -0500
@@ -2,13 +2,13 @@
Product: Mono: Compilers
Version: 1.1
OS: All
OS Details:
Status: NEW
Resolution:
-Severity:
+Severity: Unknown
Priority: Normal
Component: C#
AssignedTo: mono-bugs@ximian.com
ReportedBy: sebastien@ximian.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
@@ -90,6 +90,20 @@
+ return true;
+#endif
Error_AttributeEmitError
("SecurityAction is out of range");
return false;
}
+
+------- Additional Comments From rharinath@novell.com 2005-02-28 03:32 -------
+Well, in net_2_0_bootstrap, we ensure that mcs is run with
+supportedRuntime="v2.0.40607".
+
+That's the only change. We just us mcs as is. However, since it uses
+the 2.0 runtime, these types should be available to it when compiling
+gmcs.
+
+I think the '#ifdef NET_2_0' is inappropriate for code in 'gmcs'.
+That code almost uses mscorlib from the 2.0 profile, and so we can use
+many .Net2.0 APIs directly. However, we have to ensure such APIs are
+available under NET_2_0_BOOTSTRAP in mscorlib.
+