Re: what was the single mgmt decision made in mid-1990s that slowed the evolution of ILE/RPG? -- MIDRANGE-L

× 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.

Steve Richter wrote:

what I would like to understand is if system software architects
define the components of an OS as strictly as it appears. ILE does
this and that. nothing else. Programming languages have their own call
stacks and dont concern themselves with interoping with another
language module. Something like Java with its many useful features
like reflection, inheritance and garbage collection, is to be walled
off from the rest of the system in a JVM. SQL - same thing. The fact
that SQL procedures dont throw exceptions back to the caller when they
bomb, or dont log their activity to the joblog like CL programs do -
that is a problem. It limits the functionality of the resulting
application.

Did the ILE people in the mid 90s report to IBM mgmt that their work was done?

Probably. But so what? ILE does what it does. JVM does what it does. As
others pointed out, why the heck should they be any more tightly
integrated that they are now? Do they have to be as tightly integrated
as traditional Windows .EXE programs with CLI apps? Just to shut up some
annoying .NET programmer? Dream on!

Cheers! Hans

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.