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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78252 --- shadow/78252 2006-05-02 14:39:17.000000000 -0400 +++ shadow/78252.tmp.5450 2006-05-03 06:35:54.000000000 -0400 @@ -70,6 +70,15 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-05-02 14:39 ------- Hmm, the interesting point but I don't understand why should one switch between comliant and not compliant on regular basis. And secondly easier way is instead of removing attribute just to change its value from true to false and an assembly is not CLS compliant. + +------- Additional Comments From [EMAIL PROTECTED] 2006-05-03 06:35 ------- +When one is just copying other assemblies CLS compliance is a priori. +When developing original assemblies it isn't, and such switches often +happen. + +The second is a good point though I have never seen people writing +code like: [CLSCompliant(Consts.CLSCompliance)] + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
