× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multi-part message in MIME format...
--
To: java400-l@midrange.com
From: jamesl@hb.quik.com
X-Advert: http://emumail.com
Reply-To: jamesl@hb.quik.com
Date: Thu, 12 Dec 2002 21:06:36 AST
X-Mailer: EMUmail
Subject: Re: java to RPG problem

> I think it is only _because_ it is so similar to C that it was picked up
so
> quickly. If it had been based on PL/I it would have had the level of
>
acceptance of PL/I .......

PL/I was slow to be accepted because so few
machines of the early 1980s had the
processing power to run the compiler
(essentially the same reason why the
original mainframe ZORK was split into
three separate microcomputer games). As
wasteful of processing power as most
modern bloatware is, that's no longer an
issue . . .

A language based on
PL/I syntax would do rather well, especially if only the
PL/I jocks
recognized it as such. After all, there was an awful lot of PL/I in
the
various QBASICs of the 1990s. PL/I has the advantage that its syntax is so

straightforward as to be intuitive to anybody familiar with practically ANY

other language.

If somebody were to be elected absolute ruler of
cyberspace, and were to decree
that all software must be written in C and
C-derivatives, or worse, in RPG, I'd
go to work as a plumber, like my
dad.

Now, don't get me wrong: RPG has a useful feature: where most
languages have to
walk through files, RPG can ride around on its logic
cycle.

--
J.Lampert




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.