The place where I work teaches basic C & we're looking for a replacement for TClite, as M$ seem to be phasing out any remaining Dos-compatibility.
DevC++ seems great, but for one thing: when I open, modify & compile an existing C file, the original file seems to be overwritten (without a prompt). Is this a feature, and if so, can we turn it off? ;-)
TIA
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi, dont think so, since the compiler uses the files from the hdd. If your changes wouldn't be saved, gcc would always compile the old, unchanged sources I suppose. Make backups from your files before you touch them?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Usually, you won't want any old sources to be compiled, so it does indeed make lots of sense to save the currently opened IDE files and start the compilation then, the scenario where I could imagine this could be problematic is when you actually use another IDE/editor (or the shell) to edit your sources!?
It would probably only take 5 minutes to add such an option, however does it make sense?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
TVM for those responses.
Here's an example scenario: when I'm teaching, I try to get students to build a pgm from the ground up. First they use a printf, then a scanf (I know, I know...;-) ), then repeat a block of code 3 times, then they use a for loop instead, then an if, then an if...else, and so on.
At each step, they modiify working code, compile it, run it, and save it when it's working. With DevC++, they risk losing the workng stuff if they forget to rename and save before they test-compile. A couple of students have stopped using it for this reason.
I'm just curious - I can print a modiified document before I save the changes, Borland will let me compile a modified file, and so on, so I wondered if I was missing something.
Thanks again
Rob
:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could probably modify the Makefile so that it has two targets, one building a temporary file, however actually the 'UNDO' facility should be sufficient?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
(DevC++ 4.9.9.2.)
Hi
The place where I work teaches basic C & we're looking for a replacement for TClite, as M$ seem to be phasing out any remaining Dos-compatibility.
DevC++ seems great, but for one thing: when I open, modify & compile an existing C file, the original file seems to be overwritten (without a prompt). Is this a feature, and if so, can we turn it off? ;-)
TIA
Rob
hi, dont think so, since the compiler uses the files from the hdd. If your changes wouldn't be saved, gcc would always compile the old, unchanged sources I suppose. Make backups from your files before you touch them?
Usually, you won't want any old sources to be compiled, so it does indeed make lots of sense to save the currently opened IDE files and start the compilation then, the scenario where I could imagine this could be problematic is when you actually use another IDE/editor (or the shell) to edit your sources!?
It would probably only take 5 minutes to add such an option, however does it make sense?
TVM for those responses.
Here's an example scenario: when I'm teaching, I try to get students to build a pgm from the ground up. First they use a printf, then a scanf (I know, I know...;-) ), then repeat a block of code 3 times, then they use a for loop instead, then an if, then an if...else, and so on.
At each step, they modiify working code, compile it, run it, and save it when it's working. With DevC++, they risk losing the workng stuff if they forget to rename and save before they test-compile. A couple of students have stopped using it for this reason.
I'm just curious - I can print a modiified document before I save the changes, Borland will let me compile a modified file, and so on, so I wondered if I was missing something.
Thanks again
Rob
:
You could probably modify the Makefile so that it has two targets, one building a temporary file, however actually the 'UNDO' facility should be sufficient?
Goto Tools>Environment Options. Be sure 'Create Backup Files is unchecked. That should do it.