|
P.S. Every language except embedded SQL would have the same problem that RPG has. Namely the call is strongly typed, down to the precision and scale of the
parameters and return value. So I can't cover every possible option in a single sub-procedure regardless of the language.
Well, not *every* language. You definitely would not have that problem
in [various IBM i scripting languages, for example]
Given that the context was creating a procedure to be called from RPG to simulate %min and %max functions, yes every language that can be called from RPG as a function, and return a value, can Python even do that, would have the same issues. The reason is, and the limitation of RPG sub-procedure parameters, is that parameters are always strongly typed. I can't just say, this is a number, and any number will work. In fact, unless I use floats, I have to specify the number of decimal positions, and that precludes numbers with more decimal positions, or If I provide the maximum possible decimal positions, that severely limits the size of the integer portion of the number. And floats have their own issues since they are not exact numbers.
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.