John Denker wrote: > >> Don't use cout/cerr. Use SG_LOG with appropriate log levels. >> > > There are 2017 comparable uses of cout in FlightGear and 376 more > in SimGear. Why don't you remove some of those? When it gets > down to the point where the ones I've put in are, say, 1% of the > total, I'll consider removing them. > > > Some of these messages probably predate our logging system, others might have slipped in by accident (and I confess being guilty of of this in the past). It is our policy, however, to use the SG_LOG mechanism exclusively. Judging from the small amount of information printed during your average FlightGear session, not many of these cerr / cout statement are in code that is run frequently. The frequent ones are converted by now. Also note that many cout statements still in the code are commented out, for potential use in future development / debugging.
Personally, I don't object against commented-out cout / cerr statements in the code if the author wants to retain them for ongoing development. Submitted patches should be free of active ones, however. I have updated the "Submitting Patches" page on the WIKI in order to make this policy better known. Cheers, Durk ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
