Win32 API future ...?

Quote:

---

Originally posted by indiocolifa
With managed code , the cleaning of memory resources that the programmer allocates is done automatically by the OS (or a underlying framework such as NET). Imagine not using anymore delete[] and avoiding many (almost all) memory leaks.

---

But wouldn't that significantly reduce the programmer's level of control over the software that he's writing?

And what about stuff like OpenGL? Won't that become less useful, since much of that syntax is very similar to that of WinAPI?

Quote:

---

Originally posted by YourSurrogateGod
Is it possible to install Visual Studio .NET Academic version without those stupid updates? I don't have much hardrive space and I would really like to get around that annoying part, is there any way? Thanks in advance.

---

Which updates do you mean?
I do not know much about the academic version, but I imagine that the setup program (as with other versions) allows you choose what you want to install, so you can choose not to install C#, etc (although I think Managed C++ comes bundled with Visual C++ and thus cannot be left out of the installation).

One thing to note, there are some changes to the IDE, and the Class Wizard in .NET, that can be confusing at first.

BTW: I remember reading that Visual Studio .NET can co-exist with Visual Studio 6, so you can install it, and try it out without effecting your VS6 installation, if you want.

Quote:

---

Originally posted by YourSurrogateGod
But wouldn't that significantly reduce the programmer's level of control over the software that he's writing?

And what about stuff like OpenGL? Won't that become less useful, since much of that syntax is very similar to that of WinAPI?

---

I really do not know much about managed code, but from reading TheCPUWizard comments:

Quote:

---

Originally posted by TheCPUWizard
In fact the user can NOT overrite a buffer even if they want to (unless they mark the code as unsafe and do a few other things).

---

It sounds like you will still be able to do certain things, provided you know what your doing.

Quote:

---

Originally posted by TheCPUWizard
Windows is currently native on the WinAPI. .NET must call the API. When the next round of windows comes out, this becomes inverted (The WinAPI calls will be routed to .Net

---

The underlying .NET framework will basically be the new Windows API, and will have it's own functions in support of OpenGL, etc. Imagine learning to program windows later, without having ever learned the current Windows API, or MFC, etc, I imagine it will be much the same as learning the Windows API now (or learning to program using any new library, etc), but less error prone.

So pretty much .NET is a version of java or something? All of the little things are done for you, therefore reducing your wordload and dumbing you down?

If that is so, then why does C++ .NET need a destructor? Why not just simply get rid of all of the reserved memory when the program is done executing?

And please someone tell me that one can still program in normal C, that would make a very unhappy camper if I had to abandon that :mad: ?

One last thing that I forgot, does anyone know any good tutorials or books on C++ .NET?

I have this book...
Microsoft Visual C++ .NET Step by Step
ISBN: 0-7356-1907-7
By: Julian Templeman, Andy Olsen

... and frankly it just keeps telling you (click this button, click this checkbox, type this in the textbox that says "Program Name" and so on), that's quite irritating unless you've never programmed before in your life, and you want to learn the complete basics. I stated that before here(how childish this book is)...
http://www.codeguru.com/forum/showth...hreadid=277890 .

One more thing about C++ .NET, it has pointers, right? Don't you need to allocate memory for those things? How else can you use them(either that or assign the address of a different variable to it, but that has limited fun opportunities ;) ) without calling the malloc function or something?

Use references, not pointers! :D

Quote:

---

Originally posted by indioclifa
Use references, not pointers! :D

---

Looks like it.

altough, I must recognize that I prefer, in terms of syntax, the old pointer style... that scrambled "guru" look...

those function definitions...

VOID func (UINT* pp, void* sz, float* d, LPSTRUCTNAME** zf);

:D

anyway, I must also recognize that using references is FAR more cleaner and secure :rolleyes:

Quote:

---

Originally posted by ats007spdou
What is "Managed Code" exactly? I see you guys throw that phrase around, but what does it mean exactly?

---

check the link in my previous reply..
in brief it protects the programmer from himself..By manageing resources (memory) to disallow memory leaks..

Quote:

---

Originally posted by YourSurrogateGod
And please someone tell me that one can still program in normal C, that would make a very unhappy camper if I had to abandon that :mad: ?

---

Mmm... let's face it. I like C very much, but in the next years, the use of C will be reserved to very specific projects (such as ASM today).

C is NOT a .NET - supported language (I don't know any .NET compliant C compiler...)

go to C++, which is good because you can still use many C-ways of doing things (in managed C++ e.g, I still use a lot of structs, #defines, etc. :D :D )

IMHO, when you discover e.g std::vector and std::string you ask yourself how you done it for the past 10 years without those exciting and easy-to-program artifacts.

Please don't blame me, I know this is offtopic, but ...

anyone tried using Server 2003 as a development workstation? And in that case, how it compares (for development of course: compile times, response,etc) with WIndows XP and 2000?

thank you... and blame me if you want, my friends. :cry:

I BLAME YOU!!! YOU OFF TOPIC SETTER YOU!!! :mad:
just kidding
:D :D :D

You're right about the old way of pointers indio, it looks way cooler.

ok ok, just don't blame me.

Windows 2003 anyone?:rolleyes:

Quote:

---

Originally posted by YourSurrogateGod
I BLAME YOU!!! YOU OFF TOPIC SETTER YOU!!! :mad:
just kidding
:D :D :D

You're right about the old way of pointers indio, it looks way cooler.

---

I cannot understand how longhorn and .Net solve the performance issues without pointers. I found the programs written in C# very very slow in executing compared to C and C++. I did a few sample programs using C# in win2k and it took 5-6 seconds to print two strings.:o

Could anyone tell me the difference between Managed C++ and C#? They're both based on .NET, aren't they, but which one is the heir of our beloved C/C++? And why choose MC++ but not C#?