Stef, I'm not really sure what you are trying to do, but in Dolphin, I created a "runtime transcript" that would dump output into a file. My runtime session manager sub-classes all set the global Transcript to point to the (hopefully/intended-to-be thread-safe) file stream. I later built an application-specific logging facility that was configurable both in verbosity and in whether it went to the file or to the debug monitor (OutputDebugString()).
Speaking of OutputDebugString(), I had so many uses of it, that I created something analogous in Pharo. It notes the OS and sends ouput to syslog() on Linux. Object Arts planned to remove Transcript>>show: at one point. IIRC, they did not actually remove it, which was fine with me, because it meant that I didn't have to be bothered adding it myself :) I *think* they added a new global stream, Trace, that wrote to the transcript, so one would use things like Trace print:someObject; cr. to log. And that stream could, of course, be connected to a file for deployed executables. Just some random thoughts... Bill ________________________________________ From: [email protected] [[email protected]] on behalf of Stéphane Ducasse [[email protected]] Sent: Saturday, November 05, 2011 10:35 AM To: [email protected] Subject: Re: [Pharo-project] about name for logging message yes could be a good candidate. let us see if other suggestions arrive Stef On Nov 5, 2011, at 2:38 PM, Norbert Hartl wrote: > > Am 05.11.2011 um 12:50 schrieb Stéphane Ducasse: > >> Hi guys >> >> I introduce >> log to replace Transcript show: … >> logCr and crLog >> >> Now stupidly I did not notice that it will capture log on number :( and also >> on collection, >> >> So any suggestion of what would be a nice logging message? >> short and cool. >> > How about trace? > > Norbert
