Posted by
timothy
on from the not-the-same-as-self-flagellation dept.
Bob Smith writes: "Miguel just commited the last patch nessisary to get Mono's C# compiler to compile itself. After 7 odd months, MCS is now self hosting."jbarn adds: "Mono-list email is here."
Microsoft and "standards"
by
MosesJones
·
· Score: 2, Troll
I am well aware that MS have submitted C# to ECMA, but then they also sat on the SOAP 1.1 expert group and their implementation didn't meet the standard.
Implementing ECMA on its own is pointless,.NET is the only implementation that matters. In the same way as JBoss and Enhydra have to stick to the J2EE spec because implementing just the language spec is pointless then Mono will have to implement.NET or just become a sideline.
MS don't have a great history of backwards compatibility, they have a great history of patches that upgrade their old stuff to match the new stuff. DR-DOS, Samba et al all demonstrate the changing nature of those supposedly backwards compatible APIs.
Not being a revolution isn't a problem, but it would be nice for once if we could actually move beyond a problem set that was effectively solved around 8 years ago rather than just spinning then same one over and over again.
-- An Eye for an Eye will make the whole world blind - Gandhi
Does anyone know if MS's C# compiler is written in C#?
Business. Numbers. Money. People. Computer World.
I am well aware that MS have submitted C# to ECMA, but then they also sat on the SOAP 1.1 expert group and their implementation didn't meet the standard.
.NET is the only implementation that matters. In the same way as JBoss and Enhydra have to stick to the J2EE spec because implementing just the language spec is pointless then Mono will have to implement .NET or just become a sideline.
Implementing ECMA on its own is pointless,
MS don't have a great history of backwards compatibility, they have a great history of patches that upgrade their old stuff to match the new stuff. DR-DOS, Samba et al all demonstrate the changing nature of those supposedly backwards compatible APIs.
Not being a revolution isn't a problem, but it would be nice for once if we could actually move beyond a problem set that was effectively solved around 8 years ago rather than just spinning then same one over and over again.
An Eye for an Eye will make the whole world blind - Gandhi