> > This shouldn't increase the size of the binary at all, but is readable and > > continues to log everything we currently log. There will be 3 special > > cases though, where the string in err_msg[] takes an argument. Let me know > > what you think. > > I definitely like that. But if we're touching this, I'd like to make > sure we have a single place for all logging (and possibly tracing) > facilities, and that we're exercising p11util.c for generic pkcs#11 > stuff.
Agreed. > To speak frankly, I don't care much about __FUNCTION__, __FILE__ and > __LINE__.. Perhaps we could have a generic "log_ockerror(errorcode, > message)"? This way we could add location info as well as any other > eventual parameters. This sounds like an easy way to lose control of all the strings that we now have in a nice neat list... I'm open to counter arguments though... Kent > -Klaus > > ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
