Quake II .NET
-
I found this in Chris Sells blog: Quake II .NET[^] Derek Lakin. Try the Code Store for instant integrated access to an online repository of .NET components. I wish I was what I thought I was when I wished I was what I am. Salamander Software Ltd.
Cool, and the source code is there too! I've got to play around with this. Thanks for the link. "You're mom is nice. Mind if I go out with her?" - Jörgen Sigvardsson
-
I found this in Chris Sells blog: Quake II .NET[^] Derek Lakin. Try the Code Store for instant integrated access to an online repository of .NET components. I wish I was what I thought I was when I wished I was what I am. Salamander Software Ltd.
-
I found this in Chris Sells blog: Quake II .NET[^] Derek Lakin. Try the Code Store for instant integrated access to an online repository of .NET components. I wish I was what I thought I was when I wished I was what I am. Salamander Software Ltd.
I have had a hard time finding what was "managed" in Quake II .NET Using Reflector, I see at least 70% of the dump consisting in static exported tables (native calls). Sounds like C++ for me. By the way, not exactly what a real managed code written from scratch would show. I don't buy this.
-
I have had a hard time finding what was "managed" in Quake II .NET Using Reflector, I see at least 70% of the dump consisting in static exported tables (native calls). Sounds like C++ for me. By the way, not exactly what a real managed code written from scratch would show. I don't buy this.
-
I think their web page said that it was mixed mode (managed and unmanaged) so I'm not surprised. Rewriting the whole thing in managed code would be a huge undertaking. I'm not sure what they're trying to prove either. :confused:
I think only the "radar" add-on is written with managed code. But I don't know what the fact that overlaying a few GDI+ polygons on top of the screen leads to. The quake engine is still brutal C/C++ (pak0.pak file).
-
I have had a hard time finding what was "managed" in Quake II .NET Using Reflector, I see at least 70% of the dump consisting in static exported tables (native calls). Sounds like C++ for me. By the way, not exactly what a real managed code written from scratch would show. I don't buy this.
The point made on their web site was that C code can easily be ported to C++, and that C++ can easily be compiled to target the CLR. This implies mixed mode, which - as Microsoft states in the .NET Framework SDK docs - is intended to help developers switch to managed code easily. Mix mode at least churns-out assemblies that can be used in newer applications. While porting an .exe, this might not be the best example. Typically, such things as C++ libraries (exported functions, classes, or COM objects, etc.) can be compiled to target the CLR and then used in new, completely managed apps (i.e., written in C#, VB.NET, or many others). MC++ is more of a bridge than anything else, and I think Vertigo has shown that example well.
Reminiscent of my younger years...
10 LOAD "SCISSORS" 20 RUN
-
The point made on their web site was that C code can easily be ported to C++, and that C++ can easily be compiled to target the CLR. This implies mixed mode, which - as Microsoft states in the .NET Framework SDK docs - is intended to help developers switch to managed code easily. Mix mode at least churns-out assemblies that can be used in newer applications. While porting an .exe, this might not be the best example. Typically, such things as C++ libraries (exported functions, classes, or COM objects, etc.) can be compiled to target the CLR and then used in new, completely managed apps (i.e., written in C#, VB.NET, or many others). MC++ is more of a bridge than anything else, and I think Vertigo has shown that example well.
Reminiscent of my younger years...
10 LOAD "SCISSORS" 20 RUN
Ok Heath, Let's agree that "Quake II .NET" is teasing a lot, and that title obviously remembered us the engine it got known for. Now we know what to expect from it. God I would have liked to see how little time the GC would have taken before creepling my 256MB.
-
The point made on their web site was that C code can easily be ported to C++, and that C++ can easily be compiled to target the CLR. This implies mixed mode, which - as Microsoft states in the .NET Framework SDK docs - is intended to help developers switch to managed code easily. Mix mode at least churns-out assemblies that can be used in newer applications. While porting an .exe, this might not be the best example. Typically, such things as C++ libraries (exported functions, classes, or COM objects, etc.) can be compiled to target the CLR and then used in new, completely managed apps (i.e., written in C#, VB.NET, or many others). MC++ is more of a bridge than anything else, and I think Vertigo has shown that example well.
Reminiscent of my younger years...
10 LOAD "SCISSORS" 20 RUN
Heath Stewart wrote: MC++ is more of a bridge than anything else Regarding MC++ is a bridge, you are quite right and I hope P/Invoke had never existed by the way, just to avoid the marshaling mess.
-
I found this in Chris Sells blog: Quake II .NET[^] Derek Lakin. Try the Code Store for instant integrated access to an online repository of .NET components. I wish I was what I thought I was when I wished I was what I am. Salamander Software Ltd.
-
Thanks for posting this! I'm going to have neck surgery next week and have been wandering around looking for a game to play while horizontal. Game and more now!! ed Regulation is the substitution of error for chance.
Hope everything goes well, get well soon :)
-
The point made on their web site was that C code can easily be ported to C++, and that C++ can easily be compiled to target the CLR. This implies mixed mode, which - as Microsoft states in the .NET Framework SDK docs - is intended to help developers switch to managed code easily. Mix mode at least churns-out assemblies that can be used in newer applications. While porting an .exe, this might not be the best example. Typically, such things as C++ libraries (exported functions, classes, or COM objects, etc.) can be compiled to target the CLR and then used in new, completely managed apps (i.e., written in C#, VB.NET, or many others). MC++ is more of a bridge than anything else, and I think Vertigo has shown that example well.
Reminiscent of my younger years...
10 LOAD "SCISSORS" 20 RUN
From the Vertigo guy, http://weblogs.asp.net/cweyer/posts/9961.aspx[^] "...Porting 125k lines of C to Managed C++ took about 3 days" Now I understand his definition of managed code. ;P