× 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.



David,

That was my first thought also...

However, named variables are just address, the compiler substitutes an
address every place a variable is used right?

It seems to me it's not unreasonable for the debugger to be able to
show us a constant.

Particularly since IIRC, for a constant, the compiler simply sets the
vaule up as automatic storage and replaces the name with an address
just like a variable.

Charles

On Thu, May 13, 2010 at 4:20 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:
Mike Novak wrote:
Is there any way to display the value of a named constant in the WDSC
debug perspective.  Whenever I hover my pointer over any other variable
it shows the current value.  Can I only get the named constant value by
referring to the line where it's originally defined in the code?

Doubtful ... named constants are just that ... constants.  The compiler probably just substitutes the assigned value whenever the name is referenced.

david

--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries  (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


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.