[M3devel] initializing with subarray(constant)

[Jay]

Anyone understand this and know how to fix?
 
Maybe the test passes with older/forked tools?
I'll try it with 3.6 and maybe 4.1.
 
It's very confusing that some of the "LV" and "LValue" functions take a parameter rhs : BOOLEAN.
We end up with
Variable.LoadLValue(p.obj) where p.obj is of type Constant.T
 
The fix reveals understanding of the problem and makes the specific case work, but I think a better fix must exist.
 
I think it'd be quite excellent for NARROW() failures to print the two types involved.
Currently there isn't "room" for the data -- we call abort("narrow failed").
I put in some RTIO calls in IsSubtype to get a better handle on what is happening.
Maybe m3gdb shows types well?
I'm too impatient to build it so I make do with cdb and gdb..
 
 - Jay



> Date: Sat, 3 May 2008 10:04:55 +0000> To: m3commit at elegosoft.com> From: jkrell at elego.de> Subject: [M3commit] CVS Update: cm3> > CVSROOT: /usr/cvs> Changes by: jkrell at birch. 08/05/03 10:04:55> > Modified files:> cm3/m3-sys/m3front/src/exprs/: QualifyExpr.m3 > cm3/m3-sys/m3front/src/values/: Constant.i3 Constant.m3 > cm3/m3-sys/m3tests/src/: m3makefile > > Log message:> enough to fix test p2/p205, but needs more attention as the fix> seems to be at the wrong abstraction level and not cover every case> > in particular, confusion around lvalues vs. non-lvalues> in particular, read the comments in QualifyExpr.m3> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080503/3217cd79/attachment-0001.html>