I will volunteer for making the MSVC patches for all the areas but panel.cxx and the FDMs. The file panel.cxx has NONE defined as a macro and the chance is too high for me to mess something up in the FDMs (and they are under active development). I will also not touch type mismatches such as:
'class ssgBranch *' : forcing value to bool 'true' or 'false' Should I submit patches to you, files to Curt, or submit the patches to the group? If I am to submit patches, I would like a test run just to make sure I have the process down (I use WinCvs, and its diff output doesn' t look like I am use to seeing from others). If the FDM people think they can trust me, I can give them patches for fixing the type mismatches. There are four cases where not all control paths are covered in a function. I assume that I should not touch these, either. Jonathan Polley On Sunday, April 14, 2002, at 12:35 PM, David Megginson wrote: > Jonathan Polley writes: > >> My preference would be to have me keep the list fo MSVC build errors >> up-to-date and come up with a deadline when certain errors will be fixed >> (especially the ones in FDM\LaRCsim\ls_model.c). > > Patches are best (for me; full files if you send to Curt). If you > simply tell me about an error message, I cannot be sure that I've > fixed it correctly; if you send me a patch that eliminates the error > under MSVC, I can test it under GCC as well, and the commit if there > are no problems (and then make any fixes Erik sends in for Irix, and > then repeat the cycle). > > > All the best, > > > David > > -- > David Megginson > [EMAIL PROTECTED] > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
