I think you can just 'throw new NotSupportedException();' I wouldn't bother doing this for stuff that's in the ACMA standard. ECMA provides an XML document with the complete spec and documentation in it. It should be trivial to write an XSL stylesheet to generate the stubbed out classes with doc-comments, attributes & exceptions directly from this. I think this is exactly that Intel did with their CLR work.
I have to say that I don't think that filling out the class definitions is necessarily a good idea. I think it would be much better to leave them commented out, then when someone's adding a new feature that relies on the implementation of some method the compiler will tell them that it's not implemented as opposed to them having to track it down at runtime. ideally the only things that should throw NotImplementedExceptions are implementations of some interface methods. Piers. -----Original Message----- From: Daniel Carrera [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 11:28 PM To: Mono Mailing List Subject: [Mono-list] "Not supported" What do I do about methods that say "Not supported" on the documentation? For example: Not supported. The IList.Contains method indicates whether a specified object is contained in the list. ... [C#] public bool Contains( Image image ); ... Daniel. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
