So again you may change a file which compiles for itself, but breaks the compilation of some files which depend on ti. Or even worse - the compilation could pass, and the program could fail when started (and worst - the program could start, but the behavior to be incorrect :-)
As bottom line - run your tests every time before you check in :) 2c -- dimiter "Adam Goldband" <[EMAIL PROTECTED]> wrote in message aebuur$6vr$[EMAIL PROTECTED]">news:aebuur$6vr$[EMAIL PROTECTED]... > It's mostly a safety thing for integrating with other folks I work with. > Before I cvs a class I make sure it compiles... but sometimes I will go and > deal with other classes I depend on for this class and then come back... > except I now can't remember if I have compiled that class or not, so I have > to do it again just to be safe... > This has nothing to do with Makefile... it has more to do with that fact > that we have an auto-build system that automatically recompiles out whole > tree everytime we commit something to cvs... and if you break the build you > get harassed beyond belief... > > adam > > "Kirk Woll" <[EMAIL PROTECTED]> wrote in message > aebi20$1lh$[EMAIL PROTECTED]">news:aebi20$1lh$[EMAIL PROTECTED]... > > Out of curiosity, since the make function compiles all changed files for > > you, why would you like to know? > > > > Kirk > > > > "Adam Goldband" <[EMAIL PROTECTED]> wrote in message > > aebc31$uvp$[EMAIL PROTECTED]">news:aebc31$uvp$[EMAIL PROTECTED]... > > > Would it be possible to show some indicator somewhere in the physical > GUI > > to > > > show that the class that I am looking at has changed since the last time > I > > > compiled it? > > > > > > thanks, > > > adam > > > > > > -- > > > Adam S. Goldband > > > SE, AT, CNET, SF, USA > > > > > > > > > > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
