logging design question
I am building a C++ wrapper for a C API. So for example there is a
Widget object which encapsulates a Widget (obviously not called that).
There can be all sorts of reasons why getting/working with the widget
fails and I am wondering about logging the errors.
A) have no logging in these classes and simply return error codes?
B have no logging and just raise an exception?
C) specify a logging path in constructor for object and log to there?
|All times are GMT. The time now is 11:15 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.