ms virtual c++: yae or nae??
the software came with my textbook and i'm wondering if it is that much diff than the unix c++. iirc, the prof said we use ansi c++ program [emacs]. is there much of a difference between the two, and is it bad to switch back and forth while learning?
also, would a xxxxxx.cc program written on ms virtual c++ be readable on a unix machine?
also, would a xxxxxx.cc program written on ms virtual c++ be readable on a unix machine?
you mean visual C++?
as long as you don't use MFC, Microsoft Foundation Classes, your C++ program should compile and and run on other platforms. basically, no programs that do things with windowing systems. so a console application will be perfectly fine.
emacs is just a text editor. you will compile it with g++ or gcc or some other unix compiler. visual C++ is an IDE, integrated development environment, that provides the text editing together with the compiler, project management, and other tools in one package.
personally i prefer VI and just a bunch of terminal windows over anything else
if you write a program with visual C++ and copy the file into a unix machine it might find some funky characters in there, because windows and unix handle newline characters differently. last time i tried, however, it was fine going from windows to unix/linux, but not the other way around.
as long as you don't use MFC, Microsoft Foundation Classes, your C++ program should compile and and run on other platforms. basically, no programs that do things with windowing systems. so a console application will be perfectly fine.
emacs is just a text editor. you will compile it with g++ or gcc or some other unix compiler. visual C++ is an IDE, integrated development environment, that provides the text editing together with the compiler, project management, and other tools in one package.
personally i prefer VI and just a bunch of terminal windows over anything else
if you write a program with visual C++ and copy the file into a unix machine it might find some funky characters in there, because windows and unix handle newline characters differently. last time i tried, however, it was fine going from windows to unix/linux, but not the other way around.


