|
That wouldn't solve the problem. an "object" in an OO language can have methods (i.e. procedures) that you can call. You can declare an array of objects, or different objects of the same type, and each one has its own copy of the routines that you can call. Just allocating memory for a data structure doesn't really solve this problem. Furthermore, I'm wondering what your design accomplishes? You call a service program with an externally defined data structure, and then it does the operation that you would, otherwise, do directly. What does this save you, in terms of maintenace? Or coding? All it does is add overhead. "Eric N. Wilson" <doulos1@home.com> wrote: > I was just thinking... Perhaps you could have a service program per > file and > as the first parm you would pass the operation and as the second par > a > pointer to a DS and optionally a third parameter also a parm to a DS > The DS > could be allocated dynamically by either the service program or the > application but then you would be able to have arrays of objects and > perform > the action upon it via the parameter interface. +--- | 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-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.