{one more entry in the thread drift, and then I think I'll shut up}
On Fri, 14 Apr 2023 17:22:47 +1000, Chris Angelico <ros...@gmail.com> declaimed the following: >Yeah, the "ADDRESS" command has so much potential. Back in the day, I >built a MUD with REXX scripting, and within those scripts, the default >ADDRESS target was "send message to the invoker of the command", so >you could do something like this: I used to think (Open)VMS would have been a potential platform for an effective ADDRESS command. Where ARexx used a shared memory linked-list for the "port" (as I'd stated, avoiding copying of data), (Open)VMS had "mailboxes" (they would have to copy data -- or at best remap the virtual memory from one process to another) which could serve the same purpose; receiving application creates/owns the named mailbox, sending applications would provide the data packet including a return mailbox link. > >/* A bare string gets sent to the client */ >"Hello!" >/* You can still invoke shell commands, if you actually need to */ >address cmd "do_a_thing" > Yeah, that was the other feature -- anything that could not be parsed as a REXX statement was automatically sent to whatever the current ADDRESS host happened to be. -- https://mail.python.org/mailman/listinfo/python-list