Re: Standards question: What is your feeling about %found&%eofvs. %found(file) & %eof(file) ?

Joe Pluta wrote:

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. :)

Nice word play :-)

Not trying to switch the argument at all. Only describing why my real world code doesn't go BOOM despite not qualifying my BIFs. It turns out that my particular coding style NEVER separates the CHAIN and BIF, and under those circumstances my style doesn't harm readability.

IF I need to test the 'found/not found' condition away from the CHAIN, I always use a well named boolean, set at the point of CHAIN.

I'm not at all arguing that putting the name in the BIF is wrong, wasteful or an eyesore. Only that I've never seen a need to do it, AND that despite being against the grain of consensus, my code is easy to read and maintain because of my chosen coding style. I don't see anything wrong with putting the file name in the BIF, and having that little bit of extra 'intent' can't hurt.

It was very interesting to see that most people prefer to have the fully qualified BIF. Made me stop and think about my own choice. I could easily switch without a qualm.