Borland command line compiler issues.
My questions are about the free Borland command line compiler & tools (v5.5.1).
No it's not the usual "How do I install it all and compile a program" questions, it's all installed and running, but it does seem a bit twitchy and I was wondering how other people find it and what advice you could all offer. Perhaps some hidden and undocumented gem of information that will make my life a lot less stressful again. ;)
I recently upgraded my OS from Win95 to Win2000, and so decided to upgrade my old 16-bit Borland Turbo C 3.1 suite to a 32-bit compiler.
It should probably be stated at this point that I only program as a hobby, in C.
Why is it then that some of my old source code compiles into an executable program with no worries at all, and yet others absolutely refuse to?
All kinds of strange things are happening. In some programs the code: textcolor(LIGHTCYAN); is enough to change the colour of the output. In other programs though I've had to use the longwinded SetConsoleTextAttribute (GetStdHandle(STD_OUTPUT_HANDLE), FOREGROUND_INTENSITY | FOREGROUND_GREEN | FOREGROUND_BLUE); to achieve the same result, and for no apparent reason. If left in the original shorete form, the text of the output is plain old lightgray.
The most common problem is an error message which pops up after running a newly compiled executable which states that "The instruction at <address> referenced memory at <address>: the memory could not be read" and that the program must be terminated.
It is all so very frustrating... Please help:confused:
I'd be very interested to hear anyone elses thoughts or comments on how to tame this particular compiler.