Re: Comparing data in data structures -- RPG400-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: Comparing data in data structures
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Mon, 22 Apr 2024 11:37:48 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

On 2024-04-20 10:05 a.m., Daniel Gross wrote:

Am 20.04.2024 um 14:31 schrieb Barbara Morris <bmorris@xxxxxxxxxx>:
... The Idea assumes that a new %COMPCORR built-in function would return *ON or *OFF, but I think it would be more useful if it returned -1, 0, or 1.

-1: (ds1 is less than ds2)
0: (ds1 is equal to ds2)
1: (ds1 is greater than ds2)

But that would make it impossible to use the function like

if %compcorr(ds1:ds2);
...

If a %COMPCORR built-in function returned 0 for "equal", then you would code

if %compcorr(ds1:ds2) = 0;
// all corresponding subfields are equal
endif;

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Comparing data in data structures , Niels Liisberg

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.