×
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.
Jerry wrote:
How could an unqualified bif possibly be clearer?
It's the difference between CHAIN to get a record (data) and the plain
English words 'Get the parent account's most recent invoice.' Or 'Get
the sub-account's most recent invoice.' (information)
The file name on the CHAIN and the BIF are identical in name, but the
business process we're trying to accomplish is different. All by
itself, %found(invoice) doesn't help me figure out which business
problem I'm trying to work with.
So I agree with the position that the %found(filename) people take: it
IS clearer which file's status we're checking. But at the same time, if
we use that mechanism to separate the key list that set %found from the
logic that needs it, %found(filename) is still lacking in clarity when
compared to a named boolean, set by %found at the CHAIN.
Imagine someone posts this code, looking for help:
if %found(invoice)
..do stuff
vs
if parent_invoice
..do stuff
Which is clearer in intent? Even completely separated from the CHAIN?
--buck
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.