Re: [EXTERNAL] RE: the cycle that never ends -- MIDRANGE-L

Subject: Re: [EXTERNAL] RE: the cycle that never ends
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 13 Jun 2018 08:30:45 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 6/13/18, 7:48 AM, Jon Paris wrote:

I was one of those who wanted it removed from the RPG IV design. It
survived mostly because the logic for the cycle was already present
in the code for the SAA compiler that we were using as the base.

Without The Cycle, what (other than scatter-gather I/O, which is of far more questionable value than The Cycle is) is left to distinguish RPG from any other HLL, other than a really odd syntax?

Without The Cycle, why bother having RPG at all? Why not instead put all the time and effort that went into RPG IV into turning the OPM subset PL/I compiler into an ILE-based full implementation of the language?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: [EXTERNAL] RE: the cycle that never ends , Jon Paris
RE: [EXTERNAL] RE: the cycle that never ends , Musselman, Paul

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.