> I am aware that it is an easy mistake to make, which is why it is > important to draw people's attention to the risk of it happening, so > that they can watch out for it in future. It was not my intention to, > nor would I ever, yell at anyone for making a mistake (this would be > highly hypocritical since I goof up all the time), but I think it is > important to highlight errors when they happen so that people can avoid > them in future.
It's a hard mistake to catch because the code will compile OK on the developer's own machine. So it's not enough to say, make sure your code compiles. You also have to think very carefully and remember if you have added any new modules. With C/C++ development it's easier, because CVS knows to ignore .o files. When you do a command it lists all the files in your directory which aren't part of the CVS project, with a question mark beside them. I think this is supposed to remind you that you have some local files not part of the project. But CVS doesn't know to ignore .class files, so when we check in a Java program you get a very long list of files, all the .class files in the tree. It is easy to overlook a .java file somewhere in that page and a half of output. It's probably best to do a "cvs add" as soon as you create the module. It won't go into the repository until you check it in, so this won't break anything - it is a purely local function. Then you check it in at the same time as the other changes you make which rely on the new module. Hal _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
