Return-Path: LOJBAN%CUVMB.BITNET@vms.dc.LSOFT.COM Received: from SEGATE.SUNET.SE (segate.sunet.se [192.36.125.6]) by xiron.pc.helsinki.fi (8.6.12/8.6.9) with ESMTP id RAA13753 for ; Sun, 10 Dec 1995 17:49:38 +0200 Message-Id: <199512101549.RAA13753@xiron.pc.helsinki.fi> Received: from listmail.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v1.0a) with SMTP id F4514B7D ; Sun, 10 Dec 1995 16:49:37 +0100 Date: Sun, 10 Dec 1995 15:47:55 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: Re: TECH: PROPOSED GRAMMAR CHANGE 38: lambda via new selma'o CEhU X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1000 Lines: 19 Kris: > >> However, Lojban Central is still restricting overloading "ke'a"; how > >> would {le re do} reckon a solution in which there were two cmavo, one > >> for relative clauses ("ke'a") and one for lambda abstraction? > >I would prefer that solution over the pseudo-quantifier, but I hate to > >see a new cmavo for something that already exists and is actually so > >rare. I don't think it's overloading. > Here's an idea: make {ke'a} serve both purposes as J suggests, and > introduce two new cmavo for the poi and ka clauses specifically. In > either case you could use either {ke'a} or the specific one. The new > cmavo would be mostly to make logicians happy, as theoretical quantum > cmavo that {ke'a} represents in actual use. BUT make the new cmavo be: > {ke'a'a} and {ke'a'e} to avoid wasting good cmavo space. I haven't seen any reactions to this posted. I think it's a very very nice idea, and moreover should constitute a kind of blueprint solution to problems of this sort. --- And