Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!ucsd!pacbell.com!decwrl!bacchus.pa.dec.com!granite.pa.dec.com!mwm From: mwm@raven.pa.dec.com (Mike (Real Amigas have keyboard garages) Meyer) Newsgroups: comp.lang.rexx Subject: Re: Rexx compiler(s) Message-ID: Date: 21 Aug 90 18:30:15 GMT References: <90230.092947BOYDJ@QUCDN.BITNET> <90231.095318BOYDJ@QUCDN.BITNET> <26d00a0a-3d.4comp.lang.rexx-1@tronsbox.xei.com> Sender: news@wrl.dec.com (News) Organization: Missionaria Phonibalonica Lines: 31 In-Reply-To: akcs.erk@tronsbox.xei.com's message of 20 Aug 90 18:13:41 GMT In article <26d00a0a-3d.4comp.lang.rexx-1@tronsbox.xei.com> akcs.erk@tronsbox.xei.com (Erk) writes: I attended a seminar where some of the details of a COMPLETED REXX compiler for IBM VM/CMS were detailed. The REXX compiler: is plug compatible with interpreted REXX My sources indicate that they didn't do the INTERPRET statement. I don't call that "plug compatable." Of course, I'm one of these warped, wicked programmers who actually _use_ that statement :-). In article <26d00a0a-3d.4comp.lang.rexx-1@tronsbox.xei.com> akcs.erk@tronsbox.xei.com (Erk) writes: Not only would the _INTERPRET_ command be a tough one to implement, how about the intrinsic arrays. i.e MAIL_BOX.0 throught MAIL_BOX.#. The compiler would need to know the limitations of this and that would defeat the idealic design of REXX arrays. If you're talking about the associative nature of stemmed variables, that's old compiler technology. On the other hand, if you're talking about some feature unique to the VM/CMS implementation (I no longer have access to one, so I can't check), then could you explain it? Thanx,