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 TAA23432 for ; Wed, 18 Oct 1995 19:53:08 -0400 Message-Id: <199510182353.TAA23432@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v0.1a) with SMTP id 43C24F50 ; Wed, 18 Oct 1995 17:04:36 -0400 Date: Wed, 18 Oct 1995 19:29:31 +0100 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: Re: goi (was: "ko" considered bad) X-To: lojban@cuvmb.cc.columbia.edu To: John Cowan Status: OR X-From-Space-Date: Wed Oct 18 19:53:14 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU Xrx: > In my opinion, {goi} only makes sense when one of {ko'a, ko'e, ..., > fo'a, fo'e,..., by, cy,...} is on one side and none of those is on > the other. If {ko'a} or whatever is already defined, {goi} reassigns > it the new value. All other uses seem not quite right to me. I don't > even like {do goi la kir} or {mi goi la xorxes}, which are not needed > anyway, since they would supposedly say the same as {do no'u la kir} > or {mi no'u la xorxes}. I mainly agree with you. But {goi la} seems useful for ad hoc naming - "which shall henceforward in this text be named X". So {ti nou la bil} means "this, which is Bill", while {ti goi la bil} means "this, which will henceforward be denoted by 'Bill'". --- And