From: Curtis L. O. <cu...@fl...> - 2001-07-23 20:08:51
|
Durk Talsma writes: > In addition: Is there any documentation on using the log system? I > talked about this at LinuxTag with Alex, Wolfram and Christian, and > IIRC, most of us, if not all, confessed reverting to either using cerr > and cout statements throughout the code, or copy a working example from > another part of the code. > > A small README.loggin, describing the various levels and debug classes, > and how to change them would be a very worthwile addition to the > documentation IMHO. A readme would be a good idea. If anyone wants to submit one, I can include it. Essentially it works a lot like a cout statement (it's a macro wrapper) so instead of: cout << "Altitude = " << altitude << endl; You would do: SG_LOG( <level>, <subsystem>, "Altitude = " << altitude ); Note, you don't need the initial "<<" after the cout and the endl is added automatically. In theory, then you can select log messages based on their <level> or their <subsystem> (aka category). It's been a while now, so I don't remember how to select by category, but you can hard code in the minimum log level. It can't be that hard to add a command line option, or (preferably?) have it respond to an environment variable. Regards, Curt. -- Curtis Olson Human Factors Research Lab FlightGear Project Twin Cities cu...@hf... cu...@fl... Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org |