|
>> Okay, makes sense, so why then are the parameters for the API's defined binary? And >> the follow up question, since the API parameters are defined as binary, isn't the >> quantity/value limitation therein inheirant Parms are defined as binary because they are <grin> the term binary is generic - remember that the API is used by C, and COBOL as well as RPG. Each language then represents the binary requirement as best it can. Until the introduction of the I and U data types in RPG IV the B(inary) type was the closest you could get. The idea that it's the appropriate type to use is perpetuated by the fact that very few API writers have got round to updating their RPG examples. The limitation is not inherent since the languages in which the APIs are written (mostly C, C++, or PL/MI) are all capable of a true (i.e. integer) binary representation. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.