On Wed, 16 May 2018, Sven Schreiber wrote:
Am 15.05.2018 um 22:53 schrieb Allin Cottrell:
> Personally, I don't see much point in adding an $irf accessor (which would
> then require adding more "libset" variables); it seems to me this would
> just offer a less convenient way of doing what irf() can do at present.
In terms of functionality, yes. But I find that things are much easier to
learn, to teach, and to remember when they are consistent. So if getting $irf
is too complicated and we can't have a $irf/$fevd pair, then I would suggest
the other route and introduce an analogous fevd() function to have a matching
irf() and fevd() pair.
The args for fevd() would be:
- integer target (like irf), default 0 (meaning all)
- integer shock (like irf), default 0 (meaning all)
- bundle $system lookalike, as in the future irf(), default null
A plain call without explicit arguments would then be equivalent to the
current $fevd (which would remain in place).
Granted, irf and fevd are "twins" and they ought to match. I like your
second suggestion, introducing an fevd() function. That won't be
difficult to do.
Allin