× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Well, Scott got me wondering, what *does* DBGVIEW(*SOURCE) add to the
object?  I took one of my programs and compiled it once for each of the six
possible DBGVIEW settings:

           Program
            Object    Debug
DBGVIEW      Size     Data?
-------     ------    -----
*NONE       360448     No
*STMT       417792     Yes
*SOURCE     430080     Yes
*COPY       430080     Yes
*LIST       577536     Yes
*ALL        589824     Yes

The help on Debug Data? states:

  Indicates whether debug data was generated when this
  module was created.  If debug data exists, the module
  may be debugged using the source debugger.

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.

I'm sticking with DBGVIEW(*ALL).

db


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.