[M3commit] CVS Update: cm3

[Daniel Alejandro Benavides D.]

Hi all:
Yes, sure just that we need also for range checks and type checks, I mean, I guess the problem are not the client programs by itself if so why do you think they crashed unsafely?
The problem is to test the implementation more deeply, perhaps Tony is the best man to do that part of the job I think.
However unsafe code there is guaranteed by others to be right, I tend to feel that in those cases a more detailed test compliance is needed, I mean, we don't guarantee every platform behaves exactly as we think of it. Perhaps Jay could be indicated for that part of the job, I think.
Thanks in advance

--- El sáb, 15/1/11, Mika Nystrom <mika at elego.de> escribió:

> De: Mika Nystrom <mika at elego.de>
> Asunto: [M3commit] CVS Update: cm3
> Para: m3commit at elegosoft.com
> Fecha: sábado, 15 de enero, 2011 21:18
> CVSROOT:    /usr/cvs
> Changes by:    mika at birch.   
> 11/01/16 02:18:27
> 
> Modified files:
>     cm3/m3-libs/m3core/tests/thread/src/:
> Main.m3 
> 
> Log message:
>     give the user something to look at while
> the program runs (also shows off deadlock well)
> 
>