Sure- I'm not proposing to do a code review, just fix things as I notice them and/or the impact my development. I'm bothering you and the list right now because I'm a newbie and I don't have the historical back ground (like for xastir_snprintf). At some point I'll be more comfortable with the code and if that doesn't happen soon enough it's OK to tell me that I should stop.
...jerry On Thu, Jun 10, 2010 at 12:59 PM, Curt, WE7U <[email protected]> wrote: > On Thu, 10 Jun 2010, Jerry Dunmire wrote: > >> Great. I'll clean this up in a future patch. >> >> The 'static' qualifier does not seem to be used much in this program. >> Is that just historical, or is there something else (perhaps to make >> it easier to see the symbols in a debugger)? > > Just from my perspective, there's precious little time to get done > what needs to be done, so coding proceeds at a frantic pace. Errors > and most warnings from the compiler get fixed, some quick testing > may reveal bugs that get fixed, then it's committed to CVS. > Sometimes(?) the users find more bugs and those are fixed, hopefully > before the developer forgets the section of code he was working on. > No time/energy is allocated to doing it the "correct" or "more > correct" way. Make sense? > > I think a lot of open-source projects run in a similar manner. > Adding new features is interesting. Scanning existing code for > problems is not. Guess what gets done more by volunteer coders? > > -- > Curt, WE7U. <http://www.eskimo.com/~archer> > APRS: Where it's at! <http://www.xastir.org> > Lotto: A tax on people who are bad at math. - unknown > Windows: Microsoft's tax on computer illiterates. - WE7U. > The world DOES revolve around me: I picked the coordinate system!" > _______________________________________________ > Xastir-dev mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev > _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
