Author: autrijus
Date: Thu May 11 02:52:17 2006
New Revision: 9176
Modified:
doc/trunk/design/syn/S06.pod
Log:
* S06: but true is now spelled as but True
Modified: doc/trunk/design/syn/S06.pod
==
---
On Thursday 11 May 2006 5:52 am, [EMAIL PROTECTED] wrote:
* S06: but true is now spelled as but True
...
return $error but false if $error;
-return 0 but true;
+return 0 but True;
}
Properties are predeclared as roles and implemented as
On Thu, May 11, 2006 at 07:44:54AM -0400, Elyse M. Grasso wrote:
: Is but false now spelled but False? If not, if there a reason for the
: asymmetry?
Yes, the false value is False now, just as the true value is not True.
The reason for changing them is to avoid confusion with the built-in
true()
On Thu, May 11, 2006 at 10:24:24AM -0700, Larry Wall wrote:
function as a subset type. Constant functions are naturally 0-ary,
and in C culture tend to be uppercase anyway. So arguably, we could
have a rule or policy that 0-ary functions are generally uppercase,
not just the constant ones.
Larry Wall writes:
Yes, the false value is False now, just as the true value is not True.
It's not? I thought somebody had just said that it was?
The reason for changing them is to avoid confusion with the built-in
true() function,
Makes sense.
So arguably, we could have a rule or policy
