Re: Do you have a Road Map?

Ok perhaps "need" is the wrong word; mono clearly has an interest in
making their C# compiler and the C# language work with mono.  If
there is only one language/compiler that will work on mono, it will
be their C# compiler.

Again this clearly points out a complete misunderstanding of .Net. One
of the whole points of the CLR is to be *language neutral*.

No, I understand the whole CLR/language neutral stuff. Perhaps, what I wrote wasn't clear. If mono chose to support only one language, contrary to the whole point of CLR/language neutral stuff, they would support C#. If they only have the resources to make one language work, it would be C#. Certainly their goal is to make all of the languages that conform to the CLR work.

All
languages emit IL and it is that IL that must meet standards and that
their runtime must implement. Mono is not being implemented *at all*
against C#, it is being implemented against the CLR. 

Sure.

Indeed if they
*were* coding against C# specifically (or limiting their CLR
implementation to only the IL that can be produced by their own C#
implementation) then they would be failing miserably and deservedly so
and any sane developer would be running away from Mono as fast as
possible. 

Agreed.

If they were really doing it this way then there is no way
you could depend on Microsoft's C# compiler to be compliant with Mono
either since it may be different than Mono's, and could be changed /
enhanced at any time to implement additional CLR features.


Understood.

Which is *exactly* the same response you'll get from Microsoft if you
have a problem with code you produce using C# or VB.Net in Visual
Studiio which fails on Mono.

Yes, but if I take that C# code and compile it via mono's compiler, I would have a much better chance of getting support from the mono guys than if I took the IL from Delphi for .NET to them, IMO.

--
Brian Moelk
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.brainendeavor.com


.

Relevant Pages

  • Re: [opensuse] parse-metadata
    ... I remember when I was doing Java some time back I loved the language but I hated the runtime... ... We don't run up against unacceptable performance penalties in the work that we do, and the many advantages of the CLR mean a lot to us. ... It's the one that makes the most sense to me, though, as someone who has come up through the assembler to C to C++ path throughout my career. ... Now that I've finally gotten more involved with Linux, I'm looking forward to finding out what state mono is in. ...
    (SuSE)
  • Re: Do you have a Road Map?
    ... not a language. ... You keep confusing languages that emit CLR ... You would not be going to the C# team, but to the mono team. ... you want to have one C# code base that VS C# under windows to generate one CLR and then use the Mono project's C# compiler over there. ...
    (borland.public.delphi.non-technical)
  • Re: VB or C#
    ... Completely build on the Mono project and some personal opinions, ... lifeline you know for a program language. ... released as a standard. ...
    (microsoft.public.dotnet.general)
  • Re: VB or C#
    ... Mono is the only mature non-Windows CLR ... computer company has for ever meaned, ... a language that hasn't been officially published? ... programmers. ...
    (microsoft.public.dotnet.general)
  • Re: c# or Java???
    ... The scenario that concerns me is that Mono will end up with a great ... language implementation, but their ... or the name "Java"? ... My basic view is that .Net is too tied to Microsoft for me to ...
    (comp.programming)