|
I though I'm supposed to be able to ignore return value. I know if a procedure return indicator, compiler would okay it if I do callp. See below, it compiled fine.
Yes, that's true. It's not just indicators, though... the compiler will allow you to ignore/drop any return value. The only exception appears to be if it's an array. This might be a bug. I suggest reporting it as a bug to IBM, see what they say.
OTOH, the performance of returning 1920 bytes as a return value is abysmal. It'd be a much better idea to pass the array by reference than to return it as a return value -- it'll perform much better, and you'll be able to use options(*omit) or options(*nopass) to make the parameter optional without running into the "omitted array index" problem.
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.
midrange.com
