×
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.
On 2012/8/21 7:03 PM, Robert Houts wrote:
... It
isn't rocket science and eliminates all overhead of the service
program. I guess that efficient processing is not a concern to you.
The Integrated Language Environment is optimized to make bound calls
very very fast, with the intention that programmers can have many small
functions that call each other rather than flattening out the functions
to reduce the number of calls. So the cost of calling the two wrapper
functions could be negligible compared to the actual upper-casing work.
And I think programmer-efficiency is a factor here. Even if you set up
the copy file so all the other parameters can be used without further
setup, coding the call to the API is still more complex and error-prone
than calling the wrapper.
upper_value = CvtToUpper(some_value);
vs
QlgConvertCase(QlgConvertCase_To_Upper
: some_value
: QlgConvertCase_Temp_Output
: QlgConvertCase_Errcode_Give_Exception
: QlgConvertCase_Job_CCSID);
upper_value = %subst(QlgConvertCase_Temp_Output
: 1 : %len(value));
If I were maintaining this code, I'd much rather see the expressive call
to CvtToUpper than the somewhat obfuscated call to the API. Even though
I am completely familiar with this API, it's not immediately obvious
which is the "real" parameter, some_value.
midrange.com
