Strange compiler message

[MrT]

Hi:

BCB5. I changed some code deleting an object (form) at a different
point and of course this popped up an error when I tried to run. I
blocked out the
code with /* */. And it still popped an error at the line blocked
out. I then deleted the code and it still popped an error where the
removed code had been.

Each time I had saved the unit, compiled and ran make. I will delete the
obj and I am sure it will be fixed but this is indeed strange.

Best regards

[Chris Uzdavinis (TeamB)]

Post by MrT
BCB5. I changed some code deleting an object (form) at a different
point and of course this popped up an error when I tried to run. I
blocked out the
code with /* */. And it still popped an error at the line blocked
out. I then deleted the code and it still popped an error where the
removed code had been.

Hm. Sounds like the dependency wasn't correct, or the dependency
checker failed. Or the code was cached somewhere and not getting
marked dirty. Or something along these lines. In any case, it's a
bug. (And unfortunately, since BCB5 is so old, it probably will never
be fixed in that version. Whether it's fixed in a newer version, I
cannot tell you as I have no idea.)

[MrT]

Hi:

Deleted to obj and exe and rebuild and it is gone. Such is life, eh?

Thanks.

Post by Chris Uzdavinis (TeamB)

Post by MrT
BCB5. I changed some code deleting an object (form) at a different
point and of course this popped up an error when I tried to run. I
blocked out the
code with /* */. And it still popped an error at the line blocked
out. I then deleted the code and it still popped an error where the
removed code had been.

Hm. Sounds like the dependency wasn't correct, or the dependency
checker failed. Or the code was cached somewhere and not getting
marked dirty. Or something along these lines. In any case, it's a
bug. (And unfortunately, since BCB5 is so old, it probably will never
be fixed in that version. Whether it's fixed in a newer version, I
cannot tell you as I have no idea.)

[Leo Siefert]

Post by MrT
Deleted to obj and exe and rebuild and it is gone. Such is life, eh?

Most of the recent reports I have seen of this problem were actually
traced to an obj file with an incorrect date/time or an incorrect
system date/time. Not sure about BCB5, though - I don't really
remember having such problems in my own apps, but deleting
intermediate files is a way to solve a lot of build problems.

- Leo