| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
The Full Eiffel (.NET) | |
|
||
| Time: 12:29 EST/17:29 GMT | News Source: ActiveWin.com | Posted By: Chad Myers | ||
|
For those who have been following the progression of the .NET Framework and the multitude of languages that now run on the .NET common language specification (CLS), you'll be happy to note that there is now a full implementation of the Eiffel language on .NET. They said it couldn't be done. The CLS doesn't support multiple inheritance, or genericity, but they've found a way! One of the most interesting aspects of the Microsoft® .NET Framework is the common basis it provides for implementing many different programming languages. One of the first language technologies to benefit from this openness was Eiffel, whose implementation by Interactive Software Engineering (ISE) was, in an early version, showcased at the very first public introduction of the .NET Framework in Orlando. That initial release featured a partial version of the Eiffel language, Eiffel#, described in the original version of this article, which is now obsolete. ISE has now completed the implementation of full Eiffel on the .NET Framework and a first integration into Microsoft® Visual Studio® .NET. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 323 Last | Next |
The time now is
8:17:13 AM
ET.
Any comment problems? E-mail us |
| #1 By 1845 (12.254.129.73) at 8/5/2002 1:19:33 PM |
| Why don't you like that, John? |
| #2 By 2459 (24.206.97.178) at 8/5/2002 2:37:47 PM |
| That would be MSIL. But you probably meant CPU-specific assembly. :-) |
| #3 By 7826 (65.205.133.2) at 8/5/2002 3:21:38 PM |
|
'The CLS doesn't support multiple inheritance'
Correct me if I was wrong. C# doesn't support multiple inheritance but managed C++ does. 'Where's Assembly.Net' The whole idea of .NET is all the applications must be compiled into IL code not machine assembly code or native code. The .NET frame work will then load these managed code and translate them to native code on the fly. You won't see any tools like MASM in pure .NET. |
| #4 By 5444 (208.180.140.230) at 8/5/2002 4:45:54 PM |
|
foxbat,
you are corrected. managed c++ doesn't support multiple inheritance. at least not in safe mode. if you decide to run it in managed mode and mark that code as unsafe than Mutliple inheritance can occur. El |
| #5 By 2332 (12.105.69.158) at 8/5/2002 4:55:53 PM |
|
The CLR fully supports multiple inheritance, and you don't need to mark code as unsafe to use it.
Multiple inheritance is not in the CLS, but that only means that you shouldn't use it if you want your code to work happily with all other code on any .NET platform. If you know your code will only be used in a certain way, you can do anything you want. |
| #6 By 1845 (12.254.129.73) at 8/5/2002 7:05:36 PM |
|
I quite agree with your sentiment, John. Personally I do all my .NET work in C# if I can help it. I think of VB .NET as a dumbed-down C#. When I code in VB .NET I feel similar to signing a large check with a crayon. Yes the endorsement is valid, but certainly lacks elegance. You can do the job in VB .NET, but the lack of elegance (and consistancy) is quite annoying.
Though I agree with your sentiment as far as C# vs VB .NET goes, I don't agree with you overall. There is another platform out that (it starts with a "J") that claims to be the end all, be all of programming. It's wonderful that I don't have to be locked into using only one language, and yet still have the full abilities of the framework. If you don't like code translation, just think, if not for .NET you'd have to convert from one language to another without a common set of libraries. That would make your translation much more difficult. |
| #7 By 7826 (68.100.169.13) at 8/5/2002 8:03:12 PM |
|
eldoen,
I just made a test managed C++ code that uses multi-inheritance w/o any problem at all. The .NET CLR does not limit you to use single inheritance. It's the design of C# that rid of multiple inheritance to make the language much more easy to use and understand. C# clearly takes over VB in .NET as Rapid Development Tool. It keeps all the good stuff from VB while throw away a lot of the Basic crap. It's a cleaner, simpler to understand and use language than VB. Or you can call it a Microsoft's own version of Java. VB.NET is a bridging tool for those come from old VB world and not ready to pick up the new Language like C#. Microsoft even dumb down the VB.NET in its final beta to calm down the uproar from VB junks. |
| #8 By 5444 (208.180.140.230) at 8/6/2002 12:24:19 PM |
|
Fox,
fully managed as in the Garbage collector handles all memory issues with the program. It was my understanding that the reason that Multiple inheritance wasn't implemented in C# was because of the GC. and that being fully managed is that the Garbage collector handles all aspects of the program. While I do agree that the CLR (minus Generics) does a good job of handleing most languages some aspects in the Managed area are limited ot single inheritance. Although I have tried programming in managed C++ yes to know for sure, that is what they described in several documents. As a matter of fact, word(2000) was fully compiled in Managed C++, yet the vs.net guys said that it wasn't fully managed framework code. They didn't go into full details. but it has to do with the Garbage Collector. (part of the transcript from the .net show) ROBERT HESS: So let's take maybe a worst case scenario in that model. Let's say I'm Adobe. And I want to take some of my applications and convert them over to using the managed code and C++ and C# and so forth like that. What would you think the steps I'd want to take would be? Would you want me to just take my entire project, Photo Shop or something like that, and just recompile it for the framework? Or should I take a more gradual approach to bringing it along? I’m not meaning to put you on the spot here, because we didn’t talk about this ahead of time… CHRIS ANDERSON: I think with any project it's going to depend on the scenario. Now, recompiling the whole project with the CLR switch in C++ with managed extensions is a great solution, actually. You're not going to see a big performance problem, there's not going to be an issue there. All of your code will compile. As an internal test of how good that compiler was, we actually recompiled Word, and made sure that that level of application - that's not to say that Word's going to be managed in the near future - but we really wanted that to be a feature that would work for people on a large scale. ROBERT HESS: Okay. So you recompiled Word using the CLR switch, and out popped a version of Word that was fully managed. BRAD ABRAMS: Well, fully managed code. CHRIS ANDERSON: There's an interesting distinction there. BRAD ABRAMS: What Chris is talking about is that we recompiled instead, like the C compiler today produces X86 instructions for the Intel processor in a PE format. And when you use the \CLR switch, instead of X86 instructions that pop out, actually IL instructions pop out. And so the executable comes in a format that is native to the CLR, but until you explicitly say to, it doesn't take advantage of the Garbage Collector and some of the other features of the runtime. So it's the baby step that gets you going. So perhaps my statements were a little rash, Yes the CLR will fully compile C++, but it isn't fully compatable with the framework until it is so stated. IOW it won't be cross language compatable. So RMD statement that if you know that you are not going ot be sharing with other languages and or the features are unique to your project then the CLR could be used. But that comes to the safe and unsafe. code. If it is managed by the Garbage Collector MS considers it safe code if it can't be managed by the garbage collector it is unsafe code. so Multiple inheritance is unsafe code. At least my understanding of it. El |
|
Write Comment
Return to News |
Displaying 1 through 25 of 323 Last | Next |
The time now is
8:17:13 AM
ET.
Any comment problems? E-mail us |
