[M3devel] replacing hand.c with Modula-3?

Tony Hosking hosking at cs.purdue.edu
Thu Feb 18 03:03:33 CET 2010


Let's not get into the compatibility rathole.  Better to stay clean w.r.to current builds.

On 17 Feb 2010, at 18:47, Jay K wrote:

> 
> ?
> 
> 
> I have a little more reduction to do here (e.g. remove table or tables, at least the exported NT386-specific one; replace set_eq and ne with memcmp even for m3cg), but stuff will remain.
> 
> 
> It'd be nifty if Modula-3 functions/variables could be explicitly named for compat but I'll just go ahead and change the names and break compat. We break compat in other ways and it seems ok, unless people object (e.g. I removed m3_div because current backend doesn't generate calls to it, but it could/should be preserved for compat with older binaries).
> 
> 
> 
> - Jay
> 
> ________________________________
>> From: jay
>> 
>> 
>> I see no great reason for hand.c to be in C.
>> 
>> It should be easy to rewrite in Modula-3, using the Word interface.
>> 
>> The only question really is, what to call things?
>> 
>> M3_BUILTIN__set_union, etc.?
>> 
>> I think I see M3_BUILTIN somewhere.
>> 
>> RTHooks__set_union, etc.?
>> 
>> SomethingElse__set_union?
>> 
>> SomethingElse__somethingElse while we're at it?
>> 
>> 
>> 
>> 
>> M3Set__Union
>> 
>> M3Set__Singleton -- probably not even worth being a function
>> 
>> M3Set__Intersect
>> 
>> etc.?
>> 
>> 
>> 
>> 
>> 
>> - Jay
>> 		 	   		  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100217/38e90f41/attachment-0002.html>


More information about the M3devel mailing list