Re: *UNREF -- MIDRANGE-L

Subject: Re: *UNREF
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Tue, 09 Oct 2012 14:02:07 -0400
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 2012/10/8 1:22 PM, Matt Olson wrote:

Seems like a silly option to have when *UNREF should be the default.
Why allocate something if it is never referenced?

Note that *NOUNREF is the one that causes variables not to be allocated if they are unreferenced. *UNREF _is_ the silly default.

I don't know why unreferenced variables were defined into the program object in the first place. It might have been ok for us to just stop putting them into the program object when we made the change to add *NOUNREF, but there were a couple of compatibility scenarios, albeit extremely far-fetched.

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.