Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Turbo C++ is very old,forget it! an it doesn't support NT based operating
system like win 2k,xp.
C++ is a common language for most system.
Visual C++ is for Win32 systems and that can be used to create window based applications.
VC++ is the best with MFC.
well there isnt much difference. Visual C++ is a proprietary language of microsoft. but u should only look for ANSI/ISO standard C++. but yes if u want to do some work with MFC then u should use Visual C++
well, C++ is a programming language, and it's implemented in the form of an IDE (Integrated Development Environment) like VC++ or Turbo C++, sometimes actually not a full-blown IDE but just the compiler :wink: . Based on my experience I can tell that VC++ is just really needed when you want to take full control of windows features/facility in your development using C++ within windows, or you're developing a "system-tool" for windows, out of that purposes, you can choose whatever IDE you like.
if u want to use borland C++'s header files in VC++ that are a part of the standard C++ then yes it is possible. but u cant use borland specific header files with VC++. like u dont have a conio.h in Visual C++. u should look at the manuals of both the VC++ and borland if u are having compatibility issues.
i would say just stick to the standard template library of C++ and just learn the real ANSI/ISO standard C++. but u are free to use any header file from any vendor provided that u know the issues associated with its use
Use Borland Builder, (C++) very fast and productive, and follows the ANSI/ISO standards. M$ have their own non standard extensions. There is nothing visual about M$ Visual c++ and MFC. MFC is just wrappers around the most convoluted spagetti crap code your ever likly to see! Write "Hello World" with M$ Visual C++. It compiles up to a 500Kbyte monster?
...There is nothing visual about M$ Visual c++ and MFC. MFC is just wrappers around the most convoluted spagetti crap code your ever likly to see! Write "Hello World" with M$ Visual C++. It compiles up to a 500Kbyte monster?
You still can use turbo c++ as long as you supply right headers, libraries to the turbo c++ compiler.
Since that is a mess (companies which sell these softwares make them so) then nobody moves to the next level.
C++ is very flexible. All you need is a compiler, and link the compiled objects. What decides if application you compile is e.g. NT compatible are headers, libraries etc. you insert or link to it.
In a lot of cases VC++ for example links something you have no idea of indeed was linked.
Microsoft recommends the use of C, NOT C++, for writing device drivers for windows. C++ is a resource hungry language. C is lean and mean.
The win DDK has it's own C compiler, no other tools are needed.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
