[M3devel] Rv: Re: serial/Cygwin was Re: [M3commit] FilePosixC.c

[Daniel Alejandro Benavides D.]

Dear all:
I'm glad that Jay and all the people around are making
contributions, so we can claim that as some day there were a good
number of supported platforms nowadays we also have.
However I have
a question, but its more a suggestion, the modification Tony is
referring is not as standard as we would like since the type safety is
affected with the change introduced allowing <*EXTERNAL*>
(untrusted) functions in the INTERFACE FilePosix, it's an
implementation issue of the CM3 (IMHO it should warn) compiler, so we
may want to mark as UNSAFE INTERFACE, however doing that I think some
clients could not  claim any more they are safe so that "fix" is not
feasible.
Can you push to a lower level (as in the UNSAFE FilePosix
implementation module before committing the change) or make it
available in other Interface already available, why do we need that
change anyway?  Also IMHO we should leave out what is not POSIX (we
should not care for WIN64 although I know is needed by the C compiler
preprocessor) out of that file.
Although
I don't have the formal specification or program, but I can remember
libm3 code was specified and mechanically checked with the Extended
Static Checker Modula-3 (which is not sound also, that is could be
cheated, see
http://www.researchchannel.org/prog/displayevent.aspx?rID=2761&fID=345
),  that would be a good reason for keeping as safe as possible and
close to historical interfaces and just rework implementations (even if
they are not safe) as needed. I know that implementation is not safe
but at least having it well enough implemented the ESC/M3 checker and
the compiler would tell us the library should work Ok and is safe and
(hopefully) without the errors detected by the ESC as we care for the
details in the UNSAFE implementation.
There are any
special interfaces we should have as "standard" in the lower level
runtime (hard enough question I know), can we give some hints/ideas on
that?
Thanks in advance



--- El vie, 19/12/08, Jay <jay.krell at cornell.edu> escribió:
De: Jay <jay.krell at cornell.edu>
Asunto: Re: [M3devel] serial/Cygwin
Para: "m3devel" <m3devel at elegosoft.com>, "Tony" <hosking at cs.purdue.edu>
Fecha: viernes, 19 diciembre, 2008 1:25

> And I'll fix SOLsun/gnu.

I /think/ it is ok now -- changing my "ino_t" to
"m3_ino_t".
I'm still checking though.
And I only checked SOLgnu. I will check SOLsun.
 
 - Jay
 



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20081220/8f3a621f/attachment-0001.html>