On Mar 15, 2010, at 12:59 , Andreas Jellinghaus wrote: >> IMHO it is also important to have a difference in logging (which is usually >> done in long-running applications) and piping debug information to >> somewhere. OpenSC seems to fall into the latter category. As the name >> implies, sc_debug deals with *debugging* not logging. > > sc_debug is a #define for sc_do_log() so the name doesn't help here. For historic reasons. It is still used for debugging purposes. Developers call it out with sc_debug().
>> Debugging should normally be turned off as things should work as expected. > that is now the case. we used to have some mechanic to turn logging/debugging > on when things go wrong (with a heuristic that failed quite often), but that > code was remove a while ago. If you mean the suppress_errors scheme then this was a hack to avoid "return codes that indicated error but which did not mean an error situation" throwing garbage to stderr or error log, whichever was configured. -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
