Index: TODO
===================================================================
diff -u -re87eb2ded5035dc51ba89af4f68a0925db664024 -r5a7f6e086d300a9d0ad9178d7ea934b697708c07
--- TODO	(.../TODO)	(revision e87eb2ded5035dc51ba89af4f68a0925db664024)
+++ TODO	(.../TODO)	(revision 5a7f6e086d300a9d0ad9178d7ea934b697708c07)
@@ -4992,14 +4992,13 @@
 - use in forwarders "-frame object" instead of "-objframe" in nx
   for consistency with other calls (e.g. dispatch). Other values for
   "-frame" are not allowed. (btw, XOTcl has "-objscope")
+- deactivated "-onerror", since its semantics are expressible via
+  try/catch, and there are no regression tests for xotcl and nx,
+  and we could not find any script that uses this
 
 ========================================================================
 TODO:
 
-- Is -onerror for forwarders really needed?! Can we pull it out from
-  NX, at least? I can't see what -onerror should achieve that cannot
-  be done using catch.
-
 - Revisit nsf::*::assertion interface? Why does nsf::method::assertion
   allow for setting invariants. One would rather expect a
   ::nsf::object|class::assertion or the like?