[M3devel] [M3commit] CVS Update: cm3

Daniel Alejandro Benavides D. dabenavidesd at yahoo.es
Sun Jan 16 04:36:23 CET 2011

Hi all:
The best source of a check for both cases is a test set for Modula-3 vs C threading programs. I mean what source of it might come to crash if we allow just normal range and type checking by itself on the Modula-3 programs, just C part that we don't have, I assume the Modula-3 parts touching it are thread safe as it's the collector, if a program is to crash badly, it should crash in the Modula-3 version and be unsafely crashed at a certain level on C in some cases (sort of the exceptional cases), I'm more interested that it doesn't crash on both sides, sort of being a good M3 behaved guy, that is, what it would mean is we do have a problem on the threading library implementation (not tested, unmarked exception, or uncaught ones?), given platforms behave well, that sometimes I think they do, but we don't know, that's why we need test some assertions if so (not generate the code if you want to run assembly smoothly sure). Perhaps the best approach here is
 just to test it right goes into C mode and then is just part of the safe modules to guard type check the bad inputs or outputs ISTYPE() is a good way of doing it if you may allow me say.  
Thanks in advance.

--- El sáb, 15/1/11, Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es> escribió:

> De: Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es>
> Asunto: Re: [M3devel] [M3commit] CVS Update: cm3
> Para: m3commit at elegosoft.com, mika at elego.de, m3devel at elegosoft.com
> Fecha: sábado, 15 de enero, 2011 21:27
> 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)
> > 
> > 


More information about the M3devel mailing list