Hi im a complete novice in programming regards and i have an problem getting borland 5.5 to work at the command line. Ive changed the path and added the ilink and cfg files to the bin directory in borland and then when i tried to compile a simple program i get an error E2194, cannot find file. Im probably making a simple errror but i cant see it. Im using notepad++ to write the programs and saving them in the bin directory with a .cpp extension, any answers?
hi, i think i got it sorted, i have to type cd c:\Borland\BCC55\Bin into the command prompt and then compile using bcc32 (filename), Its annoying cos i thought changing the path in environment variables meant i wouldnt have to type in the whole file location into the command box. I want to use borland because it is basic and im a beginner.
I want to use borland because it is basic and im a beginner.
That's a reason why you should not be using it.
That compiler is not an ANSI standard C++ compiler. If you're a beginner, then it is imperative you use one that is ANSI standard. If you use that old dinosaur of a compiler, you will be coding using old, outdated, and now wrong C++ constructs. You will be scratching your head when simple C++ programs will not compile.
std::string s = "Hello World";
std::cout << s;
Try this with that old compiler. Does it comple? If not, then your compiler is basically junk.
You have Visual C++ Express, you have CodeBlocks using the MingW/g++ compiler. These are the two major compilers students of the language usually use on PC hardware that are free for use. Yes, you have modern Embarcadero compilers (which used to be Borland), but I have no idea if they are free or not.
So bottom line is that you dump Borland C++ from year 1995(!!) and use a compiler that adheres to the ANSI standard of at least 1998.
Last edited by Paul McKenzie; June 13th, 2012 at 10:21 AM.
Well not exactly the command line but in one project we have a lot of applications that are combined to make the complete system. To make it easy to build all without opening up every single sln I made a bat file using some vcbuild lines. Not as fancy as a bunch of makefiles but quite handy anyway.
I agree with John though. Building from the IDE in the normal work is far more practical than browsing log files to find lines with warnings or errors...
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan