home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.rexx
- Path: sparky!uunet!wrkgrp!ets
- From: ets@wrkgrp.COM (Edward T Spire)
- Subject: Re: Blanks, REXX, and portability...
- Message-ID: <1992Sep2.162052.25264@wrkgrp.COM>
- Organization: The Workstation Group
- References: <1992Sep1.165241.1@sejnet.sunet.se>
- Date: Wed, 2 Sep 92 16:20:52 GMT
- Lines: 33
-
- eric@sejnet.sunet.se (Eric Thomas) writes:
- : Ok Scott, say I give you a unix playstation with a copy of the source code for
- : LISTSERV (25-30k lines of REXX), and pay you by the hour to make it work under
- : unix. How much money will I save if I give you a REXX interpreter to make the
- : conversion easier?
- :
- : The answer is I'll lose money, because it will take you about 1-2 months to
- : realize it is much faster to rewrite everything in C than to try to reuse the
- : REXX code with the interpreter.
-
- 1. OS macros written in REXX (and other programs that are mostly OS
- commands) are hard to port. However...
-
- 2. REXX is also used as a general purpose programming language. Such
- programs are much easier to port. And...
-
- 3. REXX is used as a macro language for other applications (XEDIT
- and ISPF come to mind) that have themselves been "ported". XEDIT macros
- ported from CMS to Unix port very nicely indeed (since the primary
- addressible environments are very similar). Finally...
-
- 4. Even if you did need to essentially re-implement a large OS macro
- on Unix, doing it in REXX again may be your best choice. You cannot be
- as productive in C or PERL (unless you code these languages all day
- long every day, and even then I doubt it...) Hence there may well be
- some rexx code that is retained.
-
- REXX certainly adds value to new environments, and we should think
- seriously about how it will best fit into those new environments.
- Although we may not all agree, I believe we are all rapidly headed
- towards being involved in new computing platforms.
-
- -Ed
-