[Mono-dev] Mono's DateTime not implement same interfaces as .NET

Rafael Teixeira monoman at gmail.com
Thu Apr 23 11:15:21 EDT 2009

The bottom-line is: Mono decides were is the 'border' for compatibility, and
this aspect of DateTime is out of that border, as thoroughly discussed in
that thread.

Your application is working correctly: it is showing were Mono differs from
.NET, on purpose. There are other points were it also occurs, as our class
status pages also can show.


On Thu, Apr 23, 2009 at 10:19 AM, Zacman <kriss.sonic at gmail.com> wrote:

> Again I think there are two different issues:
> 1. the API that classes must follow
> 2. serialization
> The issue I point here is not related to how serialization works. It's a
> matter of "if a program faces a CLR classes and the program's logic depend
> on the classes' declaration (attributes, interfaces...), then mono classes
> should implement the same declaration as .NET ones".
> Actually, I came to this situation because the application I'm creating
> draw
> a map of classes' relationships. And I discover that my graphical chart of
> these relationships were different between Mono and .NET for DateTime...
> Then, relatively to the bug you mentioned, what I suggest should have no
> impact. Indeed it's quite easy to implement ISerializable without affecting
> Mono behavior (GetObject and the deserialization constructor would simply
> explicitly mimic what's implicitly done today)
> Do you see what I want to achieve?
> Robert Jordan wrote:
> >
> > Zacman wrote:
> >> I saw that one, but that's two different subjects. I'm not speaking
> about
> >> binary serialization or internal implementation, but about the public
> >> that classes should expose. Today the public API of the DateTime class
> >> does
> >> not match .NET one (and bug 325067 is rather about how it works
> >> internally).
> >>
> >> So DateTime could implement ISerializable the way it wants (either to
> >> solve
> >> the bug mentioned or even by doing nothing special to match current
> >> behavior), but it should implement it, no?
> >
> > The bug mentions why ISerializable is of no use. You just have
> > to go through the whole thread.
> >
> > Robert
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
> >
> --
> View this message in context:
> http://www.nabble.com/Mono%27s-DateTime-not-implement-same-interfaces-as-.NET-tp23175058p23196787.html
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Rafael "Monoman" Teixeira
"To be creative means to be in love with life. You can be creative only if
you love life enough that you want to enhance its beauty, you want to bring
a little more music to it, a little more poetry to it, a little more dance
to it."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20090423/410cb568/attachment-0001.html 

More information about the Mono-devel-list mailing list