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 UAA01516 for ; Mon, 27 Nov 1995 20:56:09 -0500 Message-Id: <199511280156.UAA01516@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 8AF11536 ; Mon, 27 Nov 1995 20:51:17 -0400 Date: Mon, 27 Nov 1995 19:49:52 -0500 Reply-To: Jorge Llambias Sender: Lojban list From: Jorge Llambias Subject: Re: TECH: PROPOSED GRAMMAR CHANGE 38: lambda via new selma'o CEhU X-To: lojban@cuvmb.cc.columbia.edu, jorge@minerva.phyast.pitt.edu To: John Cowan Status: OR X-From-Space-Date: Mon Nov 27 20:56:12 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU I'm against this change. > RATIONALE: > > Lambda quantification is needed to specify which place(s) of a "ka" > abstraction are being abstracted over. {ke'a} can do the job, and has already been used for that without inconvenience. The objection to subscripts does not apply in practice, because properties with multiple arguments are rarely if ever required. Subscripts would still be needed in general with ce'u anyway. > In early versions of this change, "ce'u" was a PA digit, which would not > require a grammatical change, but would allow lots of new kinds of > garbage. Now "ce'u" is limited to quantifying sumti and forming indefinite > descriptions. "Quantifying" is a strange word for this, since all ce'u would do is tag a sumti as a lambda variable. In fact, it is not clear what would be the difference between {le ka ce'u le ci prenu cu klama} and {le ka ce'u lo prenu cu klama}. Is the first one the property of being each of the three people that go, or just one of them? Is the default quantifier of {le} overridden by {ce'u}? What about {le ka ci le ce'u prenu cu klama}? Jorge