|
James, Personally, I'd expect the API to crash if called with too > parameters. Why? If you use CALL in RPG/400 and call another RPG program and pass more parameters than it expects, the call stack can get extra entries but the subprogram will typically just ignore them. True, you *could* have the program test the parameter count and if over the number expected issue an error. But do you write your programs that way? I test the parm count when I want parms to be optional, but only to safeguard references to unpassed values. I don't ever recall checking and issuing an error when too many are passed. This isn't like a prototyped call to a procedure interface. It is an external program call. Why would you expect the API to crash? Do you write your programs to crash if too many parameters are passed? (This isn't meant to sound holier than thou -- just an honest question. I've never seen any program which issued an error in this scenario. But perhaps I just live too sheltered of a life.) Oh, and I never once said that there are V2R3 customers > beating a path to our doorstep. It was Rob who said V2R3, though it was apparently meant to say V5R3, hence my sarcasm and :) emoticon in my tongue in cheek reply. Doug
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.