Re: Quick follow up to Barbara Morris *nounref -- MIDRANGE-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: Quick follow up to Barbara Morris *nounref
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 06 Dec 2012 15:31:40 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 12/6/2012 11:57 AM, Rpglist wrote:

Ok then I'm not getting this right. I do not have debug in the h
spec and I have *nounref defined but a couple of variables that are
not used are still appearing in the compile listing

I was under the understanding they should not

*nounref only controls whether the variables get generated into the module.

It has no effect on the listing; all variables always go into the cross reference, with a 7031 if they are not referenced.

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.