I think SAY came about because of history. In the beginning, most people using REX(X) ran it on CMS interactively and it chatted to the end user running the exec. If you wanted to write or print to a file you used execio. Today I still view "Print" as writing to a file/printer rather than a terminal
On Fri, 20 Jun 2025 at 16:29, Jon Perryman <jperr...@pacbell.net> wrote: > On Wed, 18 Jun 2025 22:59:44 -0700, Tom Brennan < > t...@tombrennansoftware.com> wrote: > > >On 6/18/2025 8:43 PM, Paul Gilmartin wrote: > >> And in BASIC, "PRINT" (still) means "Display on Terminal." > > > >That still makes more sense than "SAY" in REXX > > What would be a better word than "SAY"? Not making sense is a good thing > because it's environment dependent. UNIX stdout, batch sysout, TSO putline > (I think), CICS & IMS ????, sysrexx ???? and more. > > In the past, someone asked for IBM to create an OOREXX. Writing OOREXX was > the simple part of the design. IBM provides everything needed for each > environment and it's up to the OOREXX developers to implement the desired > environment compatible. Many of things we dislike with IBM REXX make it > compatible. E.g. a member contains all the functions instead of including > additional members like other languages. OOREXX was designed for Unix and > written in C or C++. Simply put, there is no benefit to making OOREXX for > TSO, IMS, CICS and ???. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
