[Mono-bugs] [Bug 73046][Nor] Changed - gmcs doesn't support new enums (defined in 2.0) in (security) attributes
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Sun, 20 Mar 2005 12:58:38 -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 sebastien@ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=73046
--- shadow/73046 2005-03-20 12:54:52.000000000 -0500
+++ shadow/73046.tmp.3011 2005-03-20 12:58:38.000000000 -0500
@@ -11,12 +11,13 @@
AssignedTo: mono-bugs@ximian.com
ReportedBy: sebastien@ximian.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
URL:
Summary: gmcs doesn't support new enums (defined in 2.0) in (security) attributes
+BugsThisDependsOn: 67711
Description of Problem:
mcs/gmcs don't support new SecurityAction defined in 2.0
Steps to reproduce the problem:
1. Try compiling this with gmcs
@@ -149,6 +150,15 @@
BOOTSTRAP_NET_2_0. But this hasn't fixed the original problem :(
------- Additional Comments From sebastien@ximian.com 2005-03-20 12:54 -------
Created an attachment (id=14716)
attribute.diff
+
+------- Additional Comments From sebastien@ximian.com 2005-03-20 12:58 -------
+The attached patch, by Martin and slighly modified by me, fix this
+problem (and make the code clearer). However it doesn't work for some
+actions that aren't part of the SecurityAction enum (i.e. the NonCas
+actions).
+
+IMHO typecasting their int value as a SecurityAction would be the
+"cleanest" way to add them but bug #67711 is blocking this.