Changes between Version 134 and Version 135 of IR2

Timestamp:

09/18/21 18:03:25 (5 years ago)

Author:

siegel

Comment:

--

IR2

@@ -3 +3 @@
 == Language principles ==
 
-* CIVL-IR is a subset of CIVL-C.  A CIVL-IR program is a CIVL-C program, and has the same semantics.
 * CIVL-IR should be a small language.   Whenever there is a way to express a new construct using other existing constructs, the preferred approach is to not add the new construct to the language.
 * CIVL-IR is to be as close as possible to a language representation of a CIVL "Model".   This is the lowest-level representation of a CIVL program, one appropriate for efficient (symbolic) execution and/or model checking.
@@ -15 +14 @@
 
 === Questions ===
+
+1. **Why are typedefs necessary?**
+  * Certain places require a type described by a single identifier, although maybe that is an unnecessary restriction.  Examples include instantiations of parameterized types: `mytype<T1,T2,T3>`.    They make programs shorter and easier to read and understand.   For diagnostics, you want to use the user's typedef name.
+
+1. **Why do we need parameterized structs and unions?  Isn't it enough to have parameterized typedefs?**
+Quite possibly.
 
 1. **Do variables have default initial values?**