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



hi David,

No, I can't think of a downside.

There's one thing I'm unsure of, however... How do you enable this same type of compatibility from Cobol? We know that C and CL pass the 1-byte return value this way by default. We know that RPG will pass it this way when you use ExtProc(*CL:foo). What about Cobol? I know that Cobol's default is the same as RPG's default, is there a Cobol equivalent to Extproc(*CL)?

Otherwise, I don't know of any downside besides having to recompile the existing callers.


David Gibbs wrote:
David Gibbs wrote:
I'm not sure that's correct ... if the RPG procedure has
extproc(*cl:name) defined, I *THINK* that should allow the procedure
to be called from both RPG and CL, but it will use CL return
parameter mechanism.

OK, to revisit this topic again briefly.

Can anyone think of a downside to adding the extproc(*cl:name) modifier to all prototypes that return a boolean (other than having to recompile all the callers)?

david



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.