|
> From: Steve Richter > > CLI ( common language infrastructure ) is the .NET value add that no > other platforms have. It is a specification that all .NET languages > adhere to which enables class code written in one language to be > referenced from an assembly and used in the code of another language. > CLI and assemblies are what make it possible for a function written > in C++ to be used in a java program. My big objection to this phrase is the fact that, while OS/400 has no explicit CLI, you have been able to do inter-program calls for decades, with bidirectional parameters, no less. My problem is that CLI is that from what I've seen it's all class-based. Only languages that adhere to a strict class-based syntax can play. That's a pretty serious limitation, since not all code needs classes. In fact, as we've shown over the years, quite a bit of really excellent code can be written without classes. But in any event, while CLI is nice, I consider the inter-program capability of OS/400 to be more than sufficient. Where you need class interaction, I think the RPG/Java syntax is a reasonable solution. Not as elegant as CLI, but without the restrictions either. Joe
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.