|
> Strikes me as the sort of thing that belongs in a library function > (which could be implemented as a service program): > > eval mycell = GetCell("/test.xls":"r1c1") > > IMHO, a BIF should reflect a need that a *large* proportion of RPG > programmers will have. BIFs for every conceivabe esoteric application > don't seem workable to me. This is a "catch-22". If updating spreadsheets were easier then it would be a common occurrence and if it was a common occurrence then the process to do it would become easier. I really don't have a problem with an API in a service program rather than a BIF. In fact, the first thing I do when I encounter an API I need to use, is to create an external procedure (in a service program) only passing the parms that are neccessary. Once that is done, I can then use my procedure like a BIF. The only real problem I have with APIs is the documentation. There must be a special college course that you take so that you can write impossible to understand text. At least the documentation for BIFs is understandable. Joe Teff +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.