Is there a convention for naming keywork arguments that should have a
boolean value?
When it's not a boolean, it seems the convention is
value: aValue
That doesn't seem right for booleans though. I'd end up with arguments
like
expensive: anExpensive
---
Mark Volkmann
On Fri, 2008-09-26 at 17:02 -0500, Mark Volkmann wrote:
Is there a convention for naming keywork arguments that should have a
boolean value?
When it's not a boolean, it seems the convention is
value: aValue
That doesn't seem right for booleans though. I'd end up with arguments
like
Norbert == Norbert Hartl [EMAIL PROTECTED] writes:
Norbert There is no strict rule to it but I think here the majority
Norbert follows some hint what to expect rule. That means you name
Norbert the argument after the class of the argument.
Norbert expensive: anExpensive
If I recall, according
On Fri, 2008-09-26 at 18:05 -0700, Randal L. Schwartz wrote:
Norbert == Norbert Hartl [EMAIL PROTECTED] writes:
Norbert There is no strict rule to it but I think here the majority
Norbert follows some hint what to expect rule. That means you name
Norbert the argument after the class of the
