]acre.commands and ⎕SE.acre.functions behave identically as far as possible. This includes the result, error signalling and any messages issued both to the log and to the session.
Kai has pointed out the inappropriateness of the API functions' issuing messages to the session. He calls various functions from other places including his own ]user.commands and apparently unconnected messages sometimes appear. Examination of the result of the function or error trapping can tell the caller whether it worked or not.
I can make the messaging function aware of which framework it's called from and make it behave accordingly. All messages would continue to be issued to the log but only user commands would do so to the session.
]acre.commands and ⎕SE.acre.functions behave identically as far as possible. This includes the result, error signalling and any messages issued both to the log and to the session.
Kai has pointed out the inappropriateness of the API functions' issuing messages to the session. He calls various functions from other places including his own ]user.commands and apparently unconnected messages sometimes appear. Examination of the result of the function or error trapping can tell the caller whether it worked or not.
I can make the messaging function aware of which framework it's called from and make it behave accordingly. All messages would continue to be issued to the log but only user commands would do so to the session.