[Mono-devel-list] Platform identification

Miguel de Icaza miguel at ximian.com
Sat Nov 22 12:57:50 EST 2003


> >>So could we introduce an official method of platform identification
> >>that will remain working and supported all the time?
> > 
> > 
> > 
> > Well, the issue is that we can not introduce public methods, variables
> > or definitions which are not part of the .NET Framework.  I have asked
> > everyone I have ran into to get a value allocated for Unix.  But even if
> > we get the value in .NET 1.2, it would not work for the .NET 1.1
> > profile.
> > 
> That's intreresting. But, sorry for the question, why?
> Anyway, a funny idea, if the restrictions apply to methods, variables,
> etc then what about attributes? Is at allowed to use e.g. corlib's
> AssemblyDescriptionAttribute for something unconventional? I mean what
> if on startup mono loads corlib and sets this attribute to something
> useful like OS name. Is it possible?

Well, the issue is that a program compiled on Mono would be referencing
members that do not exist on the Windows platform.  So this strategy is
designed so we can transport applications back and forth.


More information about the Mono-devel-list mailing list