Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id KAA14456 for ; Tue, 21 Nov 1995 10:07:30 -0500 Message-Id: <199511211507.KAA14456@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id B3B6DA48 ; Tue, 21 Nov 1995 10:58:07 -0400 Date: Tue, 21 Nov 1995 07:02:26 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: lambda in PA X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan Status: OR X-From-Space-Date: Tue Nov 21 10:07:33 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU If I even half understand this lambda stuff (unlikely, but what the heck) AND la and.'s concerns over the assignment of xe'u to PA, then I am inclined to agree with la. and. Specifically, members of PA are used in PA_MOI constructions, in MEX, in subscripts, and as quantifiers on sumti. So far, I have not seen any example of the proposed lambda applied to any other than the latter, and even there, I am not sure it has been applied to more than a couple of the uses of "quantifier_300" in the sumti grammar. I could be wrong, but I think all other members of PA at least in theory could have application in all of these contexts, if only because they can be used in combination with other members of PA to form a quantifier_300 that works in all contexts of the latter. If lambda is restricted to only some of these applications BY PRINCIPLE as I suspect, then it should be added as a separate selma'o and either inserted into the appropriate rules as an alternative, or added as an alternate definition of quantifier_300, with the current definition renumbered (say to 300A) for use in the MEX-internal reference to quantifier_300. lojbab