So 'orelse' is exactly like '//', except that the result of the left
side gets passed to the right side as an error message. Is there a
reason to make this exception, as opposed to altering '//' to behave
exactly like 'orelse' does?
--
Jonathan Dataweaver Lang
On Thu, Sep 06, 2007 at 01:40:20PM -0700, Jonathan Lang wrote:
: So 'orelse' is exactly like '//', except that the result of the left
: side gets passed to the right side as an error message. Is there a
: reason to make this exception, as opposed to altering '//' to behave
: exactly like 'orelse'
[EMAIL PROTECTED] wrote:
Author: larry
Date: Thu Sep 6 09:31:16 2007
New Revision: 14447
+
+C infix:andthen , proceed on success
+
+test1() andthen test2()
+
+Returns the left argument if the left argument indicates failure
+(that is, if the result is undefined). Otherwise it
+evaluates
Larry Wall wrote:
Jonathan Lang wrote:
: So 'orelse' is exactly like '//', except that the result of the left
: side gets passed to the right side as an error message. Is there a
: reason to make this exception, as opposed to altering '//' to behave
: exactly like 'orelse' does?
How 'bout,
On Thu, Sep 06, 2007 at 08:32:55PM -0400, Joe Gottman wrote:
: Do the results of andthen and orelse really bind to ANY arguments of
: the second block? If the second block has two parameters it makes more
: sense to me for the results to bind to the first parameter and nothing
: to bind to
