Bug #143

inconsistent module list when CLOSE loads itself indirectly

Added by J. Templ about 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:11/22/2016
Priority:NormalDue date:
Assignee:J. Templ% Done:


Target version:1.7.1
Forum topic:


When the CLOSE section of an unloaded module M loads itself indirectly,
e.g. by calling Kernel.ThisMod(N) for a module N that imports M, the
resulting module list contains N but not M. This leads to recursive
traps later on.

Reported by x512, 2016-11-20.


#1 Updated by D. G. Danforth almost 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF