Path: utzoo!utgpu!watmath!clyde!att!rutgers!bellcore!texbell!sugar!peter From: peter@sugar.uu.net (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Proposal for device hackers: REXX: Message-ID: <3039@sugar.uu.net> Date: 1 Dec 88 17:16:56 GMT Organization: Sugar Land Unix - Houston, TX Lines: 41 A "REXX:" device would be a big win, making it much easier to add REXX ports to programs. The way I see it working: In a 'C' program: REXXPORT = Open("REXX:name", MODE_NEWFILE); The driver enrolls "name" as if it was a REXX compatible program. In a REXX script: ADDRESS name command The REXX driver grabs the command from the REXX string and sends it to the file opened above. Back to the 'C' program: nbytes = Read(REXXPORT, buffer, maxbytes); This returns the command as a line of text from the file. Write(REXXPORT, response, nbytes); And this sends a response string back to the REXX script. Of course, you can effectively do the same thing without this by using a pipe and calling open('name', "PIPE:name", 'Write') Writeln('name',command) result = Readln('name') close('name') in your REXX script, but unfortunately I don't know of any PIPE: device that handles multiple opens/closes the way it needs to work for this application. Besides, it's ugly. -- Peter da Silva `-_-' peter@sugar.uu.net Have you hugged U your wolf today? Disclaimer: My typos are my own damn busines#!rne