Changes between Version 103 and Version 104 of IR2

Timestamp:

05/14/21 16:26:17 (5 years ago)

Author:

siegel

Comment:

--

IR2

@@ -280 +280 @@
 Create a symbolic constant named `UNDEF` for each type T.   These can be created on-the-fly, as they are needed.
 
-Every variable is initialized to the `UNDEF` of its type.   The exception is a struct, which may be initialized to a concrete struct in which each field is `UNDEF`.   (Either way will work, but the latter will probably be more effective.)
+A variable initialized with `$undef` is initialized to the `UNDEF` of its type.   The exception is a struct, which may be initialized to a concrete struct in which each field is `UNDEF`.   (Either way will work, but the latter will probably be more effective.)
 
 For a complete type T, the "undef-initializer" for T is defined as follows: if T is not an array type, the undef-initializer is defined exactly as above: either the symbolic constant `UNDEF` or a concrete struct of `UNDEF`s.   If T is the complete array type S[n], the undef-initializer is the array-lambda expression with length n and defining expression the undef-initializer for S.