|
List, Obvioulsy, it was a VERY GOOD THING that IBM went to the trouble of creating the integrated language environment. This has afforded the RPG programmer access to an unimaginable array of useful utilities - including the abiltiy to call functions that were once only accessible using C. One thing I have noticed on this list is the constant use of the question: "Does anybody have a good RPG prototype for that?" So, when IBM created the ILE, why didn't they create RPG and COBOL versions of the C standard library header files? Most API documentation displays the prototype in C and we (RPG programmers) are left to figure out what such a thing as a size_t is. The C programer just bungs a #include <someheader.h> statement at the top of their source and they're off. It's got to such a point that I'm learning C to enhance my RPG skills. Is that a good thing? On the one hand, learning C has given me a better understanding of the underlying architecture. On the other hand, it can't necessarily be a good thing to have to learn a second language in order to get some more leverage out of the first. IMHO, these standard functions cane no longer be regarded as C functions (regardless of the language they are written in). The moment IBM allowed access to the standard functions from all ILE languages, they should have provided header files for each language that was integrated. So, should RPG programmers need to learn C to better use such things as file descriptors, sockets, StdIn, StdOut, MI functions, CGI programming, etc... or should IBM provide standard header copysource files to allow all ILE languages as easy access to such functions and APIs as C programmers are afforded? Wouldn't it be nice to simply use a IBM-provided /include directive in your program to use such things a qsort, bsearch, cpybla, open, close, connect, accept, atoi, bind, etc... Your opinions are welcome. Cheers Larry
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.