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




INCLUDES are 1980s technology. If IBM has any skills remaining in
languages and ILE I vote they enable service programs to contain meta
data ( if that is what it is called ). The definitions of  prototypes,
constants, structs should all be bound in service programs with the
compiled procedures.

I'd like that even better, but it's not the way ILE works today, and there are hurdles that would have to be overcome before they could begin to make it work that way. (For example, the fact that CL doesn't support prototypes, and the fact that different languages use different calling conventions.)

Furthermore, it means a departure from existing standards. Sure, IBM can change the way RPG and CL work, but COBOL and C have to adhere to standards. You're talking about a change to all ILE languages, and as such, they'd have to depart from those standards. No other C compiler on the planet gets the prototypes from the objects they're bound to, and I'm pretty sure it's not ANSI C.

I think it'd be great if IBM would overcome those hurdles and make the capabilities available, but I think they'll just say "if you want that sort of capability, use Java."

You say that include files are 1980's technology. My response to that is that the include files we have in QSYSINC/QRPGLESRC today are 1980's technology. All I want is updated versions. It may not be a revolutionary change, but even THAT is too much for IBM.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.