[M3devel] A question for our language lawyers

[Daniel Alejandro Benavides D.]

Hi all:
if that's true that you say "relies " Init hence the MODULE is wrong (is not) to specify that.
But record rules hasn't anything to do here.
But anyway you may have a point in that record initialization are less important than record construction (c.f p.53, s2.6.8, SPwM3), and that in the array case, it might be that it is stronger the array initialization (as a declared variable) than array construction but are decided in two different cases for WITH expression, with 'a' as an a TEXT WITH non-initialization but WITH p as a READONLY array-valued expression which doesn't do what you say it needs, so you found a bug known by Jay of "incorrect" un-initialized values in m3cg, or m3cc or m3gcc or m3cgc.
In that case you might need an array of uninitialized expressions else construct the value correctly before entering the inner WITH.
Thanks in advance



--- El vie, 6/7/12, Dirk Muysers <dmuysers at hotmail.com> escribió:

De: Dirk Muysers <dmuysers at hotmail.com>
Asunto: [M3devel] A question for our language lawyers
Para: m3devel at elegosoft.com
Fecha: viernes, 6 de julio, 2012 04:23



 

The report says (2.6.9)
"The values in the array will be arbitrary values of their 
type."
 
Now,  ParseParams in its "init" method allocates an 
array of BOOLEANs
and relies on the fact that it is 
supposedly initialised with FALSE values.
 
At the other hand the report says (2.2.4)
"The constant default is a default value used 
when a record is constructed or allocated"
 
If I allocate an array of records, which statement is 
stronger:
- the array contains arbitray record values ?
- the array record fields will be initialised to their 
default values?
 
The ParseParams "init" method is obviously erroneous and 
works only
by virtue of a happy combination of 
circumstances.
But how is the report to be interpreted in the second 
case?
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120706/b48c1005/attachment-0002.html>