|
Hi all,
I was asked in an interview how I would go about coding a call to a
procedure so that no binding to that procedure would occur at compilation.
I said I would need to have the addresses of the callable procedures and I
would have a generic prototype based on a pointer that called the procedure
indicated by its address. Depending upon what the program needed to do I
would initialise that pointer so the right procedure would be called.
This was a test to get an idea of my RPG skills, but I discovered that this
was a technique favoured by the shop. I did not dare ask why would they
want to use this technique, so I'm asking : why would you really want to do
it this way? Why not just use a SELECT statement?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
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.