> void > -mono_security_enable_core_clr (void); > +mono_security_enable_core_clr (const char *prefix); > > This breaks our ABI, we can't change that function this way. > I know it's a silly requirement for a function that hardly anyone > could be using, but > breaking our ABI should not be taken lightly.
SInce the feature has effectively not been useful in the past (and will remain non-useful until we are done with the work), it is fine to break the compatibility. The entire CoreCLR stack should get a special exception for APIs exposed during the development stage. In general features of this nature should get a free pass like this one. Consider SIMD, it evolved from 2.2 to 2.4 and that was a more visible user-level library that would have likely broken more code. It changed in the past, and it will change again until we are satisfied with the API and we declare it ready for main use. Miguel. _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list