Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: Michael on February 13, 2006, 02:58:58 pm

Title: When an error has been solved, should the file be saved before re-compiling?
Post by: Michael on February 13, 2006, 02:58:58 pm
Hello,

I have remarked a small issue (C::B rev1995, Windows XP SP2). When I compile a project and get one or more errors, I correct it/them and the I re-compile the project. The issue is that I still get the same error even if I have correct it. But if I save the modified file (toolbar-->save file icon), then it is OK. I am not sure if this is a desired behaviour or not, but in my case it lead to confusion.

Sometimes, I have also remarked that C::B ask me to save (or other) a modified file. But that file has not been modified. Anyway, C::B still asks until I say to not update it. Strange :?.

Thank you.

Best wishes,
Michael
Title: Re: When an error has been solved, should the file be saved before re-compiling?
Post by: thomas on February 13, 2006, 03:05:58 pm
I only noticed that with files that are not in the project (which is quite normal, though).
Do you experience it with project files, too?
Title: Re: When an error has been solved, should the file be saved before re-compiling?
Post by: Michael on February 13, 2006, 03:08:35 pm
Do you experience it with project files, too?

Yes. I have remarked the issue by working with a project file (practically never with files w/o project).

Michael
Title: Re: When an error has been solved, should the file be saved before re-compiling?
Post by: killerbot on February 13, 2006, 03:28:28 pm
is the file with the error in the project. Example : might be a header file from outside the project (suppose you fixed a wx header ...)
Title: Re: When an error has been solved, should the file be saved before re-compiling?
Post by: Michael on February 13, 2006, 03:34:02 pm
is the file with the error in the project. Example : might be a header file from outside the project (suppose you fixed a wx header ...)

No. The file is in the project. I had this problem especially with header files, but I am not sure that the problem come from this (most of my errors where in the header files anyway :)).

Michael