[M3commit] CVS Update: cm3
Tony Hosking
hosking at cs.purdue.edu
Tue Feb 2 18:19:16 CET 2010
That's the wrong approach. A warning is not an error. The backend should be able to cope with 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 1 Feb 2010, at 20:17, Jay Krell wrote:
> CVSROOT: /usr/cvs
> Changes by: jkrell at birch. 10/02/01 20:17:28
>
> Modified files:
> cm3/m3-sys/m3front/src/values/: Variable.m3
>
> Log message:
> test case e0\e029:
>
> MODULE Main;
> TYPE Rec = RECORD a: INTEGER END;
> VAR r := Rec; (* warning: variable has type NULL *)
> BEGIN
> INC(r.a)
> END Main.
>
> followed by internal errors and an assertion failure in m3back
>
> Change warning to error, and then it never gets to the internal errors.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20100202/841ce37f/attachment-0002.html>
More information about the M3commit
mailing list