Stéphane Ducasse wrote:
> Yes could be good
>
> So you would write what
>
> Logger default
>
> we could do the same for Transcript but breaks a lot of code and
> books. but indeed using a toothpick
> could be nice.
>
> Stef
Logging uses,
self log
as the front end, and backends are configur
Yes could be good
So you would write what
Logger default
we could do the same for Transcript but breaks a lot of code and
books. but indeed using a toothpick
could be nice.
Stef
>> Hi
>>
>> I would really like that we get a threadSafeTranscript so I coded
>> one.
>> If you can comment
indeed the idea is that I do not want to see the old one around.
Stef
On Mar 29, 2009, at 10:31 PM, Keith Hodges wrote:
> Stéphane Ducasse wrote:
>> Yes but I want to kill the old crappy one. so it cannot be an
>> external
>> package :)
>>
> Why not? I thought that pharo was supposed to be mod
Stéphane Ducasse wrote:
> Yes but I want to kill the old crappy one. so it cannot be an external
> package :)
>
Why not? I thought that pharo was supposed to be modular.
Keith
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http
Michael van der Gulik wrote:
> On 3/30/09, Stéphane Ducasse wrote:
>
>> Hi
>>
>> I would really like that we get a threadSafeTranscript so I coded one.
>> If you can comment this would help me.
>>
>
> Personally, I'd replace the Transcript with a logging system. The
> global variable "Tran
On 3/30/09, Stéphane Ducasse wrote:
> Hi
>
> I would really like that we get a threadSafeTranscript so I coded one.
> If you can comment this would help me.
Personally, I'd replace the Transcript with a logging system. The
global variable "Transcript" could be replaced with a logger wrapper.
Gul
Btw, I also wrote a transcript (and workspace) as part of OB-Tools.
Lukas
On Sun, Mar 29, 2009 at 9:24 PM, Stéphane Ducasse
wrote:
> Yes but I want to kill the old crappy one. so it cannot be an external
> package :)
>
> On Mar 29, 2009, at 8:42 PM, Keith Hodges wrote:
>
>> Stéphane Ducasse wrot
Yes but I want to kill the old crappy one. so it cannot be an external
package :)
On Mar 29, 2009, at 8:42 PM, Keith Hodges wrote:
> Stéphane Ducasse wrote:
>> did you check what the semaphore critical section is protecting?
>> cr, tab, nextPutAll: and more and not protected.
>>
>> then tr
Stéphane Ducasse wrote:
> did you check what the semaphore critical section is protecting?
> cr, tab, nextPutAll: and more and not protected.
>
> then transcriptStream inherits from stream which is not threadsafe, so
> everything can happen.
> I think that having a real thread safe output i
On Mar 29, 2009, at 7:05 PM, Igor Stasenko wrote:
> 2009/3/29 Stéphane Ducasse :
>> Igor
>> your change is already in pharo :)
>> since months :)
>
> Yes, but method i changes is not related in particular to Transcript.
> The change applies to all users of PluggableTextMorph.
>
> But as for threa
Oh, TrascriptStream already uses AccessSema..
So, it should wrap a #changed: with it:
changed: param
self semaphore critical: [
super changed: param
]
2009/3/29 Igor Stasenko :
> 2009/3/29 Stéphane Ducasse :
>> Igor
>> your change is already in pharo :)
>> since months :)
>
> Yes, but met
2009/3/29 Stéphane Ducasse :
> Igor
> your change is already in pharo :)
> since months :)
Yes, but method i changes is not related in particular to Transcript.
The change applies to all users of PluggableTextMorph.
But as for thread-safe transcript, you need to be careful when you
sending #chang
Igor
your change is already in pharo :)
since months :)
Stef
On Mar 29, 2009, at 6:48 PM, Igor Stasenko wrote:
> 2009/3/29 Stéphane Ducasse :
>> did you check what the semaphore critical section is protecting?
>>cr, tab, nextPutAll: and more and not protected.
>>
>> then transcriptStream i
2009/3/29 Stéphane Ducasse :
> did you check what the semaphore critical section is protecting?
> cr, tab, nextPutAll: and more and not protected.
>
> then transcriptStream inherits from stream which is not threadsafe, so
> everything can happen.
> I think that having a real thread safe outp
did you check what the semaphore critical section is protecting?
cr, tab, nextPutAll: and more and not protected.
then transcriptStream inherits from stream which is not threadsafe, so
everything can happen.
I think that having a real thread safe output is a must.
Stef
On Mar 29, 2009,
Stéphane Ducasse wrote:
> Hi
>
> I would really like that we get a threadSafeTranscript so I coded one.
> If you can comment this would help me.
>
> Stef
What is the difference tot he exisitng one, it has an access semaphore too.
Keith
___
Pharo-proje
Hi
I would really like that we get a threadSafeTranscript so I coded one.
If you can comment this would help me.
Stef
ThreadSafeTranscript.st
Description: Binary data
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists
17 matches
Mail list logo
