Re: [Pharo-project] about name for logging message

2011-11-06 Thread David T. Lewis
It is OSProcess class>>trace and OSProcess class>>trace: so there is no conflict at all. I mentioned it only as a data point. I chose the name "trace" because it is used for debugging, and the intent is to trace the flow of execution by putting e.g. "OSProcess trace: 'the VM is about to core dump

Re: [Pharo-project] about name for logging message

2011-11-06 Thread Stefan Marr
On 06 Nov 2011, at 12:28, Stéphane Ducasse wrote: > can you publish the code and I will fill a bug entry. > May be log: was added after. This is nothing but a quick hack... I have not checked how that interacts all the stuff I am not using in the Transcript TranscriptModel>>#initialize initi

Re: [Pharo-project] about name for logging message

2011-11-06 Thread Stéphane Ducasse
In 14217 there is no TranscriptModel (I thought that we removed it from 1.3 too). There is just ThreadSafeTranscript and no log: method there and it uses a Mutex too. So what I suggest is that if you want that we update the 1.3 version provide code that we can just load. LIke that we will integ

Re: [Pharo-project] about name for logging message

2011-11-06 Thread Stéphane Ducasse
can you publish the code and I will fill a bug entry. May be log: was added after. On Nov 6, 2011, at 3:15 AM, Stefan Marr wrote: > > On 05 Nov 2011, at 22:37, Stéphane Ducasse wrote: >> >> AddEntry: is a low level api. >> Now I will check because there were some movements around transcript in

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stefan Marr
On 05 Nov 2011, at 22:37, Stéphane Ducasse wrote: > > AddEntry: is a low level api. > Now I will check because there were some movements around transcript in 1.3 > and may be some left over were not cleaned. Ok, thanks, did not see the #log: the first time I looked at the class. Is probably a

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Guillermo Polito
I like #trace: :). Other I do not like so should be #record: or #writeDown: (ugly, hehe) :P Why not just #newLine instead of #nl :(? Therer are 5 more characters but I'm happier :P... On Sat, Nov 5, 2011 at 6:37 PM, Stéphane Ducasse wrote: > Hi stefan > > > > >> self log: > >> self

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stéphane Ducasse
did you check toothpick by joseph pelrine? Because transcript is not a logger just an historical simple output place. Stef On Nov 5, 2011, at 5:00 PM, Milan Mimica wrote: > Have you thought of a decent logging system with logging levels, output > formatter and output appenders? > Current logging

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stéphane Ducasse
Hi stefan > >> self log: >> self logCr: > > Why is it a rather platform specific CR? Why not some platform independent NL > (new line)? Indeed nl is better. I used Cr because people with Transcript show: 'foo' ; cr and not nl as far as I know > And in 1.3, I found the Transcript

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stéphane Ducasse
Thanks david I do not have OSProcess at hand, but where are these messages defined? On Object? Would it be a problem for you if we define trace and trace: on Object? Stef >>> Hi guys >>> >>> I introduce >>> log to replace Transcript show: ? >>> logCr and crLog >>> >>> Now stupidly

Re: [Pharo-project] about name for logging message

2011-11-05 Thread David T. Lewis
On Sat, Nov 05, 2011 at 02:38:14PM +0100, 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 :(

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Milan Mimica
Have you thought of a decent logging system with logging levels, output formatter and output appenders? Current logging sure comes handy, but is really rudimentary. A business application must have a modern logging system, and it's not even a complex thing to do. I'm just asking whether you have di

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stefan Marr
Hi: On 05 Nov 2011, at 15:54, Stéphane Ducasse wrote: > self log: > self logCr: Why is it a rather platform specific CR? Why not some platform independent NL (new line)? And in 1.3, I found the TranscriptModel with #addEntry: which looked like the new way of doing things since #

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stéphane Ducasse
ne Ducasse > [stephane.duca...@inria.fr] > Sent: Saturday, November 05, 2011 10:35 AM > To: Pharo-project@lists.gforge.inria.fr > Subject: Re: [Pharo-project] about name for logging message > > yes could be a good candidate. > let us see if other suggestions arrive > >

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Schwab,Wilhelm K
ts.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.duca...@inria.fr] Sent: Saturday, November 05, 2011 10:35 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] about name for logging message yes could be a good cand

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Stéphane Ducasse
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 stupi

Re: [Pharo-project] about name for logging message

2011-11-05 Thread Norbert Hartl
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 logg

[Pharo-project] about name for logging message

2011-11-05 Thread 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. Stef