Thank you for responding.
> 1. The logging facility should be implemented as a singleton, i.e. > it should not be necessary to pass in a reference to a log class to > all methods/functions which might want to add a log message. Not so sure. This gives an inherent synchronization and state problem. I'm not sure it's a good idea at all that arbitrary functions manipulates global logging. Especially not if we're already planning on multiple backends. I’m also extremely skeptical to global variables – and singletons are in my opinion just glorified global variables; however I have decided I am old enough to make an exception for logging. Asking google about the topic I also get the impression that singleton is a very common pattern for log functionality. Of course the singleton logger will induce synchronization – or alternatively calling scope must make sure that only one thread/PE is actually logging. The latter was actually my loose plan. Anyway - quite a lot of work must be done anyway, and the decision of how to access the logging functionality can be deferred for quite long. Further comments appreciated. Jaokim ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
