Darren New schrieb:
> You fix the routine that needs the new parameter, and the routine that 
> has the new parameter. You compile the code. Anyone who calls the new 
> routine won't compile.

Are you *perfectly* sure about this??

This is /not/ something you want to break: Any function you happen to 
miss (because it happens to be stored in a void* pointer somewhere, or 
whatever, and you happen to be a bit too tired that night) /will/ screw 
up your running program in a beautifully obscure fashion. Welcome, 
Heisenbug!

Misusing the compiler for identifying stuff affected by code refactoring 
is a risky business.

(Other question is, how long does it take to compile? And how many 
layers of functions do you have that you'll need to repair? Let alone 
that some part involved may be a library you don't have source code 
access to.)

Post a reply to this message