[Mono-list] commented stubs in EventLog class
30 Jun 2003 20:44:04 +0200
I understand, but this means that I won't be able to distribute a single
assembly for both Mono and .NET.
It doesn't bother me that these methods are not implemented, as in our
case (log4net) that just means that the EventLogAppender doesn't work on
Mono. Which is something we can document in the docs and release notes.
It's a pity that we're not able to distribute a single assembly for both
Mono and .NET because of this, but again, I understand.
Thanks for the explanation.
On Mon, 2003-06-30 at 18:20, Jonathan Pryor wrote:
> It was done at Miguel's suggestion. He doesn't want stub methods laying
> I can think of two reasons for this:
> 1: It would be nice to assume that if your app compiles under mono,
> then it will run under mono without (too many) problems. The
> TODOAttribute breaks this assumption, as it allows code to
> compile when it won't actually run.
> An alternative solution would be to handle TODOAttribute like
> System.ObsoleteAttribute, and have mcs print out a warning/error
> message if a TODOAttribute method/property is used.
> However, (a) this would be a non-standard extension (CSC.EXE
> wouldn't behave the same way), and (b) wouldn't permit code that has
> a TODOAttribute but works, but isn't fully implemented. I believe
> I've seen code like this, so this may be an issue.
> 2: The class status page. People are more drawn to the red 'X' of "not
> implemented" than the blue Magnifying Glass of "TODO". TODO means
> "maybe it'll work, maybe not" while 'X" means "doesn't work AT ALL."
> Purely psychological, but sensible all the same.
> - Jon
> On Mon, 2003-06-30 at 12:41, Gert Driesen wrote:
> > Hi,
> > Why are all method stub (those marked with MonoTODO) commented out ?
> > Would it be possible to uncomment these ?
> > Thanks,
> > Gert
> > _______________________________________________
> > Mono-list maillist - Monoemail@example.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
> Mono-list maillist - Monofirstname.lastname@example.org