RE: Get source from object?

[Bryan Merrell <bryan.merrell@xxxxxxxxxx>]

I have also found that with any other dbgview than *List, *ShowCpy does not
work.
We use a lot of copy members so this is very important for us. 

-----Original Message-----
From: Scott Klement [mailto:rpg400-l@xxxxxxxxxxxxxxxx]
Sent: Thursday, July 15, 2004 3:04 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Get source from object?



> I think this is misleading, because the source debugger does not show any
> source or listing for programs created with DBGVIEW(*STMT).  It is a small
> step better than *NONE in that it can still be debugged.

*STMT means "statement".  The only thing you can view in debug are the
statement numbers.  This is what we had in the old days, before the
debugger displayed the source on the screen for you...  back when you had
to refer to the compile listing to see where you were in the program..

>
> I'm sticking with DBGVIEW(*ALL).
>

I started out using DBGVIEW(*ALL) but ran into some errors where the
compiler would say "Internal Error" and generate pages and pages of memory
dumps and only really lovely things.  It didn't do that all the time, but
occasionally it would, depending on the code I wrote.

Switching to DBGVIEW(*LIST) solved the problem for me -- so that's what I
always use now.  I'm curious why you'd want the *COPY listing view
included when you've got the *LIST view included as well?  Not that *COPY
is a bad thing, it just seems superfluous when you've got *LIST.

At any rate, the problem I had was many years ago, and was probably fixed
long, long ago....   Now I just use *LIST because it's been my habit...

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.