[M3devel] [M3commit] CVS Update: cm3

[Tony Hosking]

I assume the argument here is the same as for the POSIX interfaces.

Sent from my iPhone

On Jul 21, 2009, at 1:53 PM, jay.krell at cornell.edu wrote:

> I might have left it able to be called safe. Honestly I look more  
> for human verifiable safety and correctness and it lacked those  
> before and now does not. If that coincides with machine verifable  
> safety, great. Either way you need C here for correctness and  
> safety. It isn't 'nasty'. Not using C here would be nasty. I think  
> you have it backwards. UNLESS the sizes and constants here are well  
> known but reading docs quickly I didn't see that. Unsafe does not  
> imply not portable.
>
> - Jay (phone)
>
> On Jul 21, 2009, at 9:03 AM, Tony Hosking <hosking at cs.purdue.edu>  
> wrote:
>
>> Hear, hear!
>>
>>
>> Sent from my iPhone
>>
>> On Jul 21, 2009, at 11:17 AM, "Randy Coleburn"  
>> <rcoleburn at scires.com> wrote:
>>
>>> Granted, I see that Term.m3 is an UNSAFE module, so that by  
>>> definition means it is not portable.
>>> Why though do we want to replace it by nasty C code where non- 
>>> portable stuff can be easily hidden?  This is Modula-3.  Why not  
>>> fix the Modula-3 code so that it doesn't have to be UNSAFE?  (My 2  
>>> cents.)
>>> --Randy
>>>
>>> >>> Jay Krell <jkrell at elego.de> 7/21/2009 11:55 AM >>>
>>> CVSROOT:/usr/cvs
>>> Changes by:jkrell at birch.09/07/21 11:55:36
>>>
>>> Added files:
>>> cm3/caltech-parser/term/src/: TermC.c
>>>
>>> Log message:
>>> initial copy of dangerous non portable Term.m3 to rewrite portably  
>>> and have it do nothing silently on Win32 which should suffice, or  
>>> if not, can probably be done better, specifically the MakeRaw  
>>> function
>>>
>>>
>>