Received: from uga.cc.uga.edu by nfs1.digex.net with SMTP id AA09231 (5.67b8/IDA-1.5 for ); Mon, 21 Nov 1994 15:18:32 -0500 Message-Id: <199411212018.AA09231@nfs1.digex.net> Received: from UGA.CC.UGA.EDU by uga.cc.uga.edu (IBM VM SMTP V2R2) with BSMTP id 2864; Mon, 21 Nov 94 15:19:29 EST Received: from UGA.CC.UGA.EDU (NJE origin LISTSERV@UGA) by UGA.CC.UGA.EDU (LMail V1.2a/1.8a) with BSMTP id 0010; Mon, 21 Nov 1994 13:49:27 -0500 Date: Mon, 21 Nov 1994 20:45:57 +0200 Reply-To: veion@XIRON.PC.HELSINKI.FI Sender: Lojban list From: Veijo Vilva Subject: Re: PROPOSAL: Lambda Notation For Dummies (and & Rosta) & Lojban X-To: lojban@cuvmb.cc.columbia.edu To: Bob LeChevalier Status: RO X-From-Space-Date: Mon Nov 21 15:18:38 1994 X-From-Space-Address: LOJBAN%CUVMB.BITNET@uga.cc.uga.edu la xorxes. cusku di'e > Date: Fri, 18 Nov 1994 20:48:56 EST > From: Jorge Llambias > Subject: Re: PROPOSAL: Lambda Notation For Dummies (and & Rosta) & Lojban > Is there any use for properties with two lambda variables? And in any case, > here we could use subscripts if such a thing really ever comes up. How about statements involving symmetry, like *do zmadu mi leka xa'eda ctuca xa'ede fo la lojban *le gapru cu filmau le cnita leka klama xa'eda xa'ede There are probably other uses for two lambda variables, maybe even for three, once we realize the possibilities offered by their availability. ----- BTW what happens if we stick a 'lambda quantifier' to a normal bridi? i.e. *mi nitcu xa'eda poi tanxe or even **mi nitcu xa'e tanxe > Jorge co'o mi'e veion --------------------------------- .i mi du la'o sy. Veijo Vilva sy. ---------------------------------