|
Hmm.. Okay, that makes perfect sense. You can't optimize I/O routines very much at all, that that's mostly what RPG turns out to be. Okay, I think I'll look at what I have to do to get PDM to set the DBGVIEW to *ALL. And, no, I do not plan on making that a part of my backup strategy, just something to help me to be able to retrieve the source code and to debug programs (I hate having to recompile each program twice when I want to debug it, once with DBGVIEW *ALL and then again with DBGVIEW *STMT [the default] once I'm done debugging). Regards, Jim Langston boldt@ca.ibm.com wrote: > The optimization is done by the common back-end used by > all AS/400 compilers. The optimizer is quite aggressive > and can make a difference in compute-bound applications, > especially those written in C. > > RPG semantics, however, limit the amount of optimization > that are possible. This normally isn't that big a deal > anyways since most RPG apps are I/O-bound, not compute- > bound. Since the most aggressive optimizations don't > apply to most RPG programs, debugging is not too badly > affected by the optimizations. > > Cheers! Hans +--- | 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.