Hi Al, hi list. my impression is that ELEMENTs are intended to be stateless, at least apart from minimal simulation specific data (times, matrix entries, some history).
three examples for behavioural models need to store extra data. a switch needs to know its state and switch time, the controlled oscillator needs to know its phase, and IR-filters need to stash their history. currently, this is crudely worked around in the filters, and appearantly a bug in the oscillator (bm_switch doesn't exist yet). imho, giving up those (potential) models would be too bad, so ELEMENT needs to be enhanced somehow. i'd like to give it a try, if you haven't already worked out something. ideas, objections, warnings are welcome. thanks felix _______________________________________________ Gnucap-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnucap-devel
