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 now' " in various methods ;) Dave On Sat, Nov 05, 2011 at 10:35:36PM +0100, St?phane Ducasse wrote: > 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 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? > > > > In OSProcess, #trace and #trace: are used for a similar purpose. > > This is intended for debugging with "transcript" output coming > > from the VM and therefore less dependent on process scheduling > > in the image. > > > > Dave > > > > >
