|
There were a lot of things that could have been done to leverage the
architecture. For example, we had externally described files. We
occasionally suggested the concept of externally described modules.
But it always came down to funding. Anything substantial takes
resources. With the first RPG IV release, we were able to put a lot of
good stuff into the language. I'll always cherish my memories of working
on that project, and what we were able to accomplish. After that, we had
a couple more major items to implement. But once they were done, RPG was
pretty much back into maintenance mode, albeit with a couple of
enhancements each release. At each release, we had to choose what we
considered the most important items given the constraints. Thus, the old
$100 surveys.
Frankly, I'm still amazed that /FREE made it into the language. There
was so much controversy over that one feature that I gave it less than a
50/50 chance of seeing release. Later, I was able to leverage that into
some nice free-form I/O features. But /FREE still left me jaded and
cynical. (Or rather, more so!)
But to answer in a different way, note that the languages with the
powerful features are primarily interpreted languages. In the past, I
often argued that compiled languages are not well suited for application
programming. ......
My point here is that interpreted languages are just so much easier to
enhance with powerful features. And that makes them much better suited
to application development.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.