|
Jim, <snip> >Hmm.. thinking on it though, wouldn't it be MUCH simpler to just >take the output from a compile and process that? You already have >all the cross reference information you need in there nicely laid >out for you. It tells you all the member names for each physical >file, all the variable names, where each is defined/referanced, etc... > >Why reinvent the wheel? In fact, I seem to recall, I could be >mistaken, that you can compile without actually creating the program. >Have your program run a compile without building and then read the >spool file and process it. Using the spool file will work. Actually, since the compiler knows what is and isn't used, wouldn't it be nice to have a compile option to specified "Deleted Unreferenced". : - ) I just checked out the spool file. I could just list those lines with *RNF7031 on them but that would include all of the file fields that are not being used in the program, and there are quite a few of those. Marc Zylka +--- | 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-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.