to avoid a dependency related problem in the xml files.
T0 and T0y, one of them have the OPdependent flag set
which surpresses variable declarations to be emited.
to avoid a dependency related problem in the xml files.
T1 and T1y, one of them have the OPdependent flag set
which surpresses variable declarations to be emited.
to avoid a dependency related problem in the xml files.
T2 and T2y, one of them have the OPdependent flag set
which surpresses variable declarations to be emited.
to avoid a dependency related problem in the xml files.
T3 and T3y, one of them have the OPdependent flag set
which surpresses variable declarations to be emited.
currently each and every device specific instance and model structure
duplicates the memory layout of a struct GENmodel / GENinstance
further the first structure elements behind a GENinstance header
are reinterpreted as a sort of a generic "node" array.
This business is very error prone, and makes it difficult to
extend struct GENmodel / struct GENinstance.
This patch makes this business much more bearable.
loop over DEVmodDelete() and DEVdelete() in CKTdestroy()
instead of doing this business in the DEVdestroy() functions.
As a consequence, most DEVdestroy() functions
collapse completely.
This patch itself is not valid until all invokers of DEVdestroy()
(currently this is CKTdestroy() exclusively)
are rewritten to invoke DEVmodDelete() and DEVdelete()
Instead of searching and then deleting a given device-model,
just delete the given model.
The search shall be done somewhere else.
Don't free the model struct itself,
this shall be done by the invoker himself.
Don't free the device instrance list,
this shall be done by the invoker himself.
As a consequence, most DEVmodDelete() functions
collapse almost completely.
This change is of no consequence,
because DEVmodDelete() is currently nowhere used.
Instead of searching and then deleting a given device-instance,
just delete the given instance.
The search shall be done somewhere else.
Don't free the instance struct itself,
this shall be done by the invoker.
As a consequence most DEVdelete() functions
collapse almost completely.
This change is of no consequence,
because DEVdelete() is currently nowhere used.
rlar
Guilherme Brondani Torri