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: Daniel Gross <daniel@xxxxxxxx>
Date: Sat, 20 Apr 2024 16:44:36 +0200
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>

Am 20.04.2024 um 16:35 schrieb Vern Hamberg via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx>:

Just wondering, for comparing several subfields individually, which is what I think this would be, what defines less or greater? I can see some subfields less than, others greater than.

Yes - I really do think, that the idea of a "comparator function" makes sense for that case.

Whereas for an "%isequal-corr" function this wouldn't be necessary - it can simply only compare the subfields that are present in both data structures - and return true (*on) when they are equal in both structures.

Daniel

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Comparing data in data structures , Barbara Morris

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.