[M3devel] [M3commit] CVS Update: cm3

Tony Hosking hosking at cs.purdue.edu
Mon Aug 30 15:58:36 CEST 2010


This code using NARROW in RecordType.m3 is unfortunate.  Should you not implement the "declare" method for Field.T instead, and then invoke Value.Declare on it?


Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On 30 Aug 2010, at 03:09, Jay K wrote:

> 
> diff attached
> 
>  - Jay
> 
> ----------------------------------------
>> Date: Mon, 30 Aug 2010 09:01:11 +0000
>> To: m3commit at elegosoft.com
>> From: jkrell at elego.de
>> Subject: [M3commit] CVS Update: cm3
>> 
>> CVSROOT: /usr/cvs
>> Changes by: jkrell at birch. 10/08/30 09:01:11
>> 
>> Modified files:
>> cm3/m3-sys/m3front/src/values/: Field.i3 Field.m3
>> cm3/m3-sys/m3front/src/types/: Type.m3 RecordType.m3
>> cm3/m3-sys/m3front/src/builtinOps/: BitSize.m3
>> 
>> Log message:
>> Pass more type information to backend. Hopefully it will use it.
>> 
>> In particular, if you imported:
>> 
>> TYPE Foo = RECORD a:INTEGER; END:
>> 
>> and you also defined yourself unrelated:
>> 
>> TYPE Bar = RECORD a:INTEGER; END;
>> 
>> then the anonymous "RECORD a:INTEGER END;"
>> 
>> would not be described to the backend.
>> 
> 		 	   		  <more_typeinfo_to_backend.txt>

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


More information about the M3devel mailing list