Return-Path: X-Sender: a.rosta@dtn.ntl.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_4_1); 28 Sep 2001 21:53:33 -0000 Received: (qmail 35855 invoked from network); 28 Sep 2001 21:53:33 -0000 Received: from unknown (10.1.10.142) by 10.1.1.221 with QMQP; 28 Sep 2001 21:53:33 -0000 Received: from unknown (HELO mta03-svc.ntlworld.com) (62.253.162.43) by mta3 with SMTP; 28 Sep 2001 21:54:57 -0000 Received: from andrew ([62.253.88.199]) by mta03-svc.ntlworld.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010928215454.CGOM23687.mta03-svc.ntlworld.com@andrew> for ; Fri, 28 Sep 2001 22:54:54 +0100 Reply-To: To: "lojban" Subject: RE: [lojban] The Pleasures of goi (was: zipf computations &experimentalcmavo Date: Fri, 28 Sep 2001 22:54:11 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal From: "And Rosta" X-Yahoo-Message-Num: 11173 Content-Length: 835 Lines: 29 xod: > On Thu, 27 Sep 2001, Craig wrote: > > > >da'o wipes all variables, so we need a way to reassign just one, right? > > > > How about an experimental cmavo? I propose goi'a, which functions as you are > > claiming goi should. > > Well, how about using goi for always reassignment, and no'u for the > alternative. > > ko'a goi la fred. li'o .i ko'a goi la djan. > A is Fred. ... Now A is John. (Fred is not John, A has new meaning.) > > > ko'a goi la fred. li'o .i ko'a no'uji'a la djan. > A is Fred. ... A also is John, lo, John is Fred! > > Since no'u doesn't reassign ko'a, but explains it, this is equal to > offering a new fact about ko'a as it exists. We should use goi for assignment in general, not just for reassignment, and no'u for stating coreference, which may or may not have defining function. --And.