You have a few approaches available:

1) Make each plug-in a separate program

2) Make each plug-in a separate procedure

3) Both of the above

In both cases you need an external repository to hold the definitions for each condition and which plug-in to invoke. If the plug-in is a program then a simple dynamic program call will work. If it is a procedure then you'll need to package them in one or more service programs. You'll have to use APIs to either invoke the procedure for you or return a pointer to the procedure.
See the QZRUCLSP API and the QleGetExp API in the Program and CL 
Command API section of the Information Centre.
A standard keyed database file would suffice for the repository but you 
could use other things like a user index.
Note this is not using 'call-backs'. A call-back is a function in your 
main or your plug-in that is callable from one of the other plug-ins. 
You may need to provide call-backs to complete this process and if so 
you would pass a procedure pointer to one or more call-back functions 
in the plug-in interface (or you could put the call-back functions in a 
service program and require the plug-ins to bind to it). Lots of 
options.
Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 copyright@midrange.com.

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.