The new AddCommandHandler() API allows for registering direct and redirecting command handlers from
C++ (in addition to have become able to define redirecting command handlers as a new option for
RexxCreateInterpreter).
Now that command handlers can be added at runtime (which is really a great new feature) it would be
helpful, if at least at the native side an API was made available that would allow for getting a
list of the currently defined command handlers returned with the name, the type and the native
pointer to the callback function (DirectCommandHandler/RedirectingCommandHandler) such that one
could distinguish the callback function from one's own callback function.
---
Currently thinking about how to make this ability available such, that Java programs can also be
used as redirecting command handlers (as has already been possible with command handlers).
In this context one possibility that can occur in theory (and earlier or later also in reality) is
the following situation: some Java command handler is registered and then a C++ handler by the same
name gets registered replacing the Java handler without the Java side noticing this such that it
does not get removed which might pose a problem in 7/24 deployment situations. So it might become
important to learn about such a situation to allow for removing a stale Java handler on the Java side.
If it was possible to learn about the currently registered command handlers and their callback
addresses one can find out, whether a handler callback got replaced in the meantime by a different
handler.
What do you think?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
