|
>> I'm sorry, but I can't agree with you. ILE stands for Integrated Language Environment. Agreed. But that's where we part company. Actually ILE does exist on other platforms to some degree - that's why the ILE APIs are named CEE.... it stands for Common Execution Environment. Not sure if it is still available for the PC platform, but it was probably only OS/2 anyway. One reason why the compiler on the 400 is known as ILE RPG is because those of us who were involved in the naming process were looking in the wrong direction when some dingbat took the name of the compiler package (i.e. the one that incorporated RPG IV, RPG/400, RPG/38, etc.) and slapped it on the RPG IV compiler. This was daft because now there was no distinction between the package name and one of its components. Considerable customer confusion resulted and there were many people who thought they could no longer get the old compilers. Perhaps more importantly, it conveyed the mistaken idea that you could _only_ run RPG IV programs if you went into full ILE. As you stated that is not true, but there are very few things in the RPG IV _language_ that you can't do in pseudo-OPM. Interestingly enough, the things you can't do (like subprocedures) _are_ supported by VARPG and others. It is only the OS/400 related things like AGs that you can't use - and they aren't part of the language. Many people stayed away from RPG IV because of the implication that you had to run in ILE and that is partly why I (and many others) refuse to use the stupid ILE RPG name and prefer to refer to it as RPG IV. We can argue semantics 'til the cows come home, but since most people think of ILE RPG in terms of the syntax of the language, I find nothing wrong with saying that VARPG uses "ILE RPG". What else
As an Amazon Associate we earn from qualifying purchases.
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.