From slobin@ice.ru Tue Mar 21 06:07:12 2000
Received: (qmail 19584 invoked from network); 21 Mar 2000 14:07:34 -0000
Received: from unknown (10.1.10.26) by m1.onelist.org with QMQP; 21 Mar 2000 14:07:34 -0000
Received: from unknown (HELO fair.fe.msk.ru) (194.247.147.11) by mta1.onelist.com with SMTP; 21 Mar 2000 14:07:32 -0000
Received: from localhost (slobin@localhost) by fair.fe.msk.ru (8.9.3/8.9.3/Debian/GNU) with ESMTP id RAA12119 for <lojban@onelist.com>; Tue, 21 Mar 2000 17:07:30 +0300
Date: Tue, 21 Mar 2000 17:07:30 +0300 (MSK)
X-Sender: slobin@fair.fe.msk.ru
To: lojban@onelist.com
Subject: use and abuse of sets
Message-ID: <Pine.LNX.4.10.10003211706450.10359-100000@fair.fe.msk.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-eGroups-From: Cyril Slobin <slobin@ice.ru>
From: Cyril Slobin <slobin@ice.ru>

[la xorxes. puzu cusku di'e]

> suggests sets. {mi'o} is {mi joi do}, so if only sets were
> allowed with {simxu} you couldn't say something like
> {mi'o daxysi'u}, you'd have to say {mi ce do daxysi'u}.

In fact {lu'i mi'o}. I've remembered your letter while actually typing:

{lu'i do le'e mlatu ce gerku cu simsa le ka prami simxu}

I do always prefer strong-typed programming languages, so it is very
natural for me that set is similar to set in quality of being {simxu}.

[co'o mi'e kir. noi ranji fa lenu ke'a tadni]

-- 
Cyril Slobin <slobin@ice.ru>


