|
>> Might be a good tool to write. Follows call path and compares parms along the way. Why bother? Convert the CALLs and CALLBs to CALLP and use a prototype - problem disappears! It might be worth the effort of developing a tool that examines all *ENTRY PLISTs and determines what parms are expected and then build the prototypes from that. After all - right or wrong it is what the called program defines the parm as that matters - not the callers view of it. Jon Paris Partner400
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.