Re: WDSC Debugger - Display Named Constants -- WDSCI-L

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

Subject: Re: WDSC Debugger - Display Named Constants
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Fri, 14 May 2010 08:46:59 -0500
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

Charles Wilt wrote:

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.

Dunno for sure ... but I suspect the compiler treats the named constant NUMERIC_ZERO the same as it would for *ZERO or 0. It's still a constant and not a variable, and the compiler is aware of that.

david

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.