... | ... | @@ -18,7 +18,8 @@ irf_calibration; |
|
|
y(1:4), e_ys, [0, 1];
|
|
|
end;
|
|
|
```
|
|
|
2. The Dynare macro-processor now allows for nested arrays, i.e. defining arrays that contain other arrays. As a consequence, the old ambiguous syntax needed to be replaced by something unambiguous. In Dynare `4.5`, `[1:2]` was equivalent to `1:2`. Both definitions created an array of integers. In Dynare `4.6` this has changed. `1:2` still creates an array of integers, while `[1:2]` will create an array *within *an array. This implies that in most cases the squared brackets around ranges need to be removed if algebra is performed on the array members. For example, in Dynare `4.5` you could sum integers by writing
|
|
|
2. The results of the `conditional_forecast` command are now saved in the output structure `oo_` under `oo_.conditional_forecast`. They are not saved to hard-disk in a file called `conditional_forecasts.mat` anymore. Code needs to be adjusted to reference the structure subfield instead of loading it from the disk.
|
|
|
3. The Dynare macro-processor now allows for nested arrays, i.e. defining arrays that contain other arrays. As a consequence, the old ambiguous syntax needed to be replaced by something unambiguous. In Dynare `4.5`, `[1:2]` was equivalent to `1:2`. Both definitions created an array of integers. In Dynare `4.6` this has changed. `1:2` still creates an array of integers, while `[1:2]` will create an array *within *an array. This implies that in most cases the squared brackets around ranges need to be removed if algebra is performed on the array members. For example, in Dynare `4.5` you could sum integers by writing
|
|
|
```
|
|
|
@#define a = 3
|
|
|
@#for i in [1:4]
|
... | ... | |