Re(4): My coding guidelines

in reply to Re: Re: Re: My coding guidelines
in thread My coding guidelines

If not, why not? What do you use instead? I find not is usually the cleanest and most readable operator for all sorts of tests.

It's just a matter of taste. I'm not against using not, I just don't happen to prefer it.

You give the following example:

print "$pattern not found in $file\n" if not $found;
[download]

In this case I would use unless:

print "$pattern not found in $file\n" unless $found;
[download]

As for if (not -r $file) {...}, I typically use the bang operator (!) rather than not -- just a matter of preference, probably due to my C influences.

Matt

Comment on Re(4): My coding guidelines Select or Download Code

Replies are listed 'Best First'.
Re^5: My coding guidelines by Aristotle (Chancellor) on Nov 30, 2002 at 18:18 UTC
`print "$pattern not found in $file\n" unless $found;` I use `unless` when I expect that the `print` will be executed most of the time - unless the condition happens to be true. In the quoted case, I'd probably use `if not`, as the `if` highlights the fact that the message is only printed if the pattern wasn't found. Just like the way you use "if" and "unless" in English. Makeshifts last the longest.	[reply] [d/l]
Re: Re(4): My coding guidelines by helgi (Hermit) on Dec 02, 2002 at 16:27 UTC
I prefer never to use the ! operator if I can possibly avoid it. It is much easier for me to miss when skimming through code and my brain doesn't parse it autmoatically like it does "not". For much the same reason I always prefer "or" to "\|\|" and "and" to "&&". My brain already knows how to parse these English words and I don't need to teach it new tricks. -- Regards, Helgi Briem helgi AT decode DOT is	[reply]

In Section Meditations