Hi Hendrik, > > the more I looked into this, the more I think this stuff needs a massive > > cleanup. It is a grown debug structure and it is not really helpful and > > simple at the moment. Any ideas or should I go with your patch for now? > > Grown? I think it's pretty simple as it only contains two macros. But maybe > you have a deeper insight. What do you think is broken with the current one? > You may as well call log_debug() something else, I just couldn't think of > another name as the debug output is its main usage.
before 1.0.0 we merged various debug possibilities and I don't think that it is very clean at the moment. However I have no idea what is the best debug method for a library. So I am open for suggestions. We can also leave it this way if everybody is happy. Regards Marcel ------------------------------------------------------------------------- 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 _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
