Re: Regarding retrieving source from modules

Okay, as Jon pointed out, it was optimizations I am concerned about.

I know in the PC world, anyway, if I optimize something, I can loose some
debug info.  That is, if it optimizes 3 lines of code into one line of ASM,
in this case MI I guess, then when debugging things don't step along as
they should.

So, does the RPG compiler optimize the executable?  Or is that either not
possible, or an additional step I need to perform?  If the RPG compiler
doesn't optimize my code, then it is a non issue and I can go ahead and
compile with *ALL (since there is practically no size increase over *LIST).

And this CPROBJ (which I have never used before, nor heard of).  Does
that just remove the debugging information?  Or is that what actually does
the optimization?

Regards,

Jim Langston

Jon.Paris@halinfo.it wrote:

>  >> My only convert with compiling with DBGVIEW(*LIST) or (*ALL) is the
> executable size increase.
>
> Unlike PC (and other software) there is no increase in executable size for a
> program with debug data.  Debug information is only brought into memory when 
>the
> program is being debugged.  The only reason for removing it is to reduce DASD
> occupancy or (if you are a software vendor) to stop customers from seeing how
> truly horrible your code is <vbg>
>
> The only increase is in DASD usage for the compiled program - this can be
> reduced (to less than the corresponding OPM program size in some cases) by
> compressing the observability information using CPROBJ.

+---
| 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
+---