× 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.




Joe Pluta wrote:
hate to argue this point, but the qualified BIF is absolutely clearer because it doesn't require me to read another line of code to figure out what it does. It's sort of a slam dunk. Any other argument is based on making life easier for the original programmer.

If I do a CHAIN at line 100, then at line 500 do a IF %FOUND(CUSTHIST), it's going to be difficult to immediately understand which key list was used to set that %FOUND. It's not possible to read that one line of code and know whether I'm working with parent accounts or sub-accounts. The file name alone isn't enough information.

Setting a boolean with a decent name is much clearer here than the bald file name on the BIF:
parent_account chain custhist
if %found()
parent_found=*on
else...
...
exsr processa

Whoa there, big fella. I never once said anything for or against booleans. Booleans are fine and dandy, but they have nothing to do with the decision of whether or not to qualify a BIF.

Stick to the argument or else go yank someone else's CHAIN. :)

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.