| Ticket UUID: | e593adf103ea27b765400ef588d49bb6f47ae7f0 | ||
| Title: | Resources of a namespace are still available after the namespace is deleted. | ||
| Type: | Bug | Created on: | 2018-01-02 12:32:23 |
| Submitter: | pooryorick | Assigned to: | nobody |
| Subsystem: | 18. Commands M-Z | Severity: | Important |
| Priority: | 5 Medium | Last modified: | 2018-01-06 19:17:26 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | trunk | ||
| Description: | ||||
|
The following script does not fail:
While this is known and documented, it's not ideal. The current behaviour is probably a concession to the subtleties of resource cleanup, particularly where object systems built on namespaces are involved. In commit [3825265b17], namespace cleanup routines are simplified and rationalized. Once a namespace is deleted, the global namespace becomes the current namespace. A namespace is considered deleted once all traces and routines associated with the deletion are complete. Until that time, the namespace remains available and fully functional. One effect of these changes is that in a coroutine The | ||||
