>> Object >> log should be packaged in a logging package since it's a >> convenience method >> > > No, that's not the idea at all. Object >> log and Null provide > a very lightweight discarding logging framework. We would like > it in the kernel so that no matter where a package winds up, it > can always do logging, but it may be discarded. After the > package Logging is loaded, the user or release team can decide > where the logs go (transcript, stdout, and syslog are currently > implemented) > > See http://wiki.squeak.org/squeak/3706 for the documentation on > the logging framework. > The idea is to promote the use of logging throughout the image using the following convention.
self log <subsystem> param1: value1 param2: value2. Thus removing Transcript show: from all over the kernel, and in the process provide more control (filtering, output options etc) via the chosen logging framework. Defining Object-#log ^ Null is the easiest way of implementing a NullLogger in a minimal image. However it is expected that a normal image such as Pharo would be provided with a Transcript logger as the default option. Goran's SLLog provides Transcript, File and Syslog output. Toothpick is also supported as a backend. The other complication is that I designed the logging framework with the intention of using the ProcessSpecific package whereby each process has its own buffer for the text being logged, thus avoiding any form of blocking semaphores etc. Including ProcessSpecific in the main image is another topic for discussion. Keith _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
