[M3devel] elminating pthread_attr_t from cloned headers

[Daniel Alejandro Benavides D.]

Hi all;
I guess there was a 1995 try to change that Runtime error into an exception (not sure if they succeed). Take a look at:
ftp://ftp.u-aizu.ac.jp/pub/lang/Modula/m3/pkg/contrib/whenNEWfails/src/
Please
be patient if the files don't appear when loading the web page (I tried
2 times to open that url with the source files). Hope this helps.
Thanks

--- El mié, 4/2/09, Mika Nystrom <mika at async.caltech.edu> escribió:
De: Mika Nystrom <mika at async.caltech.edu>
Asunto: Re: [M3devel] elminating pthread_attr_t from cloned headers
Para: "Jay" <jay.krell at cornell.edu>
CC: m3devel at elegosoft.com
Fecha: miércoles, 4 febrero, 2009 11:33

Jay writes:
....
>I'll maybe review more code along these lines.
>I gather the general gist of things in Modula-3 though
>is that out of memory is fatal anyway. Raising an exception
>vs. failing an assertion probably not significantly different
>if the exception is not meant to be caught and isn't ever caught.
>(Strange though then the gymnastics I pointed out elsewhere
>converting one form of out of memory to another form..)
....

Back in SRC days I remember there was a discussion at some length
about what to do in case of running out of memory.  I think the
project was abandoned as people realized it was quite a tricky
problem...

I don't believe PM3 has out of memory exceptions, nor did SRC
M3...?  It's a wild guess but maybe this has something to do with
the Critical Mass modifications for their JVM?

     Mika



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090205/5ac0b6a6/attachment-0002.html>