|
I fully agree. A set of BIF that are simply a wrapper to the posix functions should not be very hard to implement, and it will be a great helt to write clear RPG code that uses the IFS in a consistent way. And better yet, the manual will have the documentations along with the rest of the RPG BIFs. Richard B Baird wrote: > Put me in the 'make it part of the language' camp. > > as others have stated, when dealing with the APIs, there are more than a > hundred ways to skin a cat, and when having to deal with someone elses > implementation of the complicated and many times obscure API interfaces, it > becomes difficult to descern just HOW a particular implementation of an API > is supposed to behave. > > The date manipulation bifs and opcodes are a great example of this. > > It would be nice to have a common, predictable and easily understood way of > accessing stream files. Even (Hans :) if they are only wrappers for the > standard posix functions. What's the point you ask? Standardization and > ease of use. And shedding light on the cloudy IFS world to many, many > middle-of-the-road developers who would otherwise never even consider it. > > my two cents, > > rick
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.