On Wed, Dec 30, 2009 at 02:11:18PM -0600, Guangcong Luo wrote: > On Wed, Dec 30, 2009 at 6:20 AM, Per Inge Mathisen > <[email protected]> wrote: > > On Wed, Dec 30, 2009 at 6:07 AM, <[email protected]> wrote: > >> 2.3: Make VTOLs finish patrolling/scouting before returning to rearm. > > > > Perhaps try to compile your commits before you do them? > > I use Mac OS X and Windows. On Mac OS X and Windows, we do not compile > with -Werror by default, and we can't since our libraries (and Xcode's > 10.4 SDK itself; Apple doesn't support old versions of their OS very > well) generate warnings. So most of my commits have been tested and > compile just fine on my machine, and the number of warnings vary > depending on the conditions in which builds are compiles, so it can be > difficult to tell if my changes add warnings. > > If you have any advice along those lines, I'd be willing to listen, of course.
Some suggestions: Compilers have facilities to turn warnings on and off. Except for the times when your code is actually broken, most of the problems seem to be warnings like unused variables. You can add specific warning flags if the defaults are not displaying them. Your compiler docs are your friend here. Grep thru the compiler output to filter out noise. Use a chain of filters to reduce noise and/or look for specific warnings. If the above are too difficult, you could submit patches and let others test them for you. Or perhaps, simply not commit stuff after 2300 local time. -- Stephen Swaney [email protected] _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
