From sentto-44114-2816-959017450-mark=kli.org@returns.onelist.com Mon May 22 17:43:13 2000 Return-Path: Delivered-To: shoulson-kli@meson.org Received: (qmail 16681 invoked from network); 22 May 2000 17:43:11 -0000 Received: from zash.lupine.org (205.186.156.18) by pi.meson.org with SMTP; 22 May 2000 17:43:11 -0000 Received: (qmail 21043 invoked by uid 40001); 22 May 2000 17:44:14 -0000 Delivered-To: kli-mark@kli.org Received: (qmail 21040 invoked from network); 22 May 2000 17:44:13 -0000 Received: from c3.egroups.com (207.138.41.143) by zash.lupine.org with SMTP; 22 May 2000 17:44:13 -0000 X-eGroups-Return: sentto-44114-2816-959017450-mark=kli.org@returns.onelist.com Received: from [10.1.10.35] by c3.egroups.com with NNFMP; 22 May 2000 17:44:12 -0000 Received: (qmail 13778 invoked from network); 22 May 2000 17:44:08 -0000 Received: from unknown (10.1.10.27) by m1.onelist.org with QMQP; 22 May 2000 17:44:08 -0000 Received: from unknown (HELO stmpy.cais.net) (205.252.14.63) by mta2 with SMTP; 22 May 2000 17:44:08 -0000 Received: from bob (209-8-89-171.dynamic.cais.com [209.8.89.171]) by stmpy.cais.net (8.8.8/8.8.8) with ESMTP id NAA28793 for ; Mon, 22 May 2000 13:42:24 -0400 (EDT) Message-Id: <4.2.2.20000522134022.00b168c0@127.0.0.1> X-Sender: vir1036/pop.cais.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 To: lojban@egroups.com In-Reply-To: <39296707.A3D40886@concentric.net> References: <200005220306.XAA19855@calum.csclub.uwaterloo.ca> From: "Bob LeChevalier (lojbab)" MIME-Version: 1.0 Mailing-List: list lojban@egroups.com; contact lojban-owner@egroups.com Delivered-To: mailing list lojban@egroups.com Precedence: bulk List-Unsubscribe: Date: Mon, 22 May 2000 13:45:58 -0400 Subject: Re: [lojban] More on lojban programatic semantics: Strong typing and inferencing of types Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit At 12:58 PM 05/22/2000 -0400, Brook Conner wrote: > > Why not use the mekso variable declaration constructs? > >Because not all variables are mekso. A file isn't a mekso. Neither is a >string. > >Or are you suggesting that we use "operator overloading" kinds of things >for variables that aren't numbers or numerical expressions? The mekso grammar was specifically designed to allow such overloading. Almost any grammatical construct can be converted into a mekso component of some (probably appropriate) type. I specifically had in mind the possible use of Lojban as a program specification language as were appearing in the 80s as automated design tools. For a while I was tangentially involved in program proving for security purposes, and considered the requirements for mekso and Lojban to support such efforts as well. In particular, there is no requirement that mekso operate on numbers. String operations like concatenation certainly can be expressed using mathematical language. lojbab ---- lojbab lojbab@lojban.org Bob LeChevalier, President, The Logical Language Group, Inc. 2904 Beau Lane, Fairfax VA 22031-1303 USA 703-385-0273 Artificial language Loglan/Lojban: http://www.lojban.org ------------------------------------------------------------------------ WRITERS WANTED! Themestream allows ALL writers to publish their articles on the Web, reach thousands of interested readers, and get paid in cash for their work. Click below: http://click.egroups.com/1/3840/3/_/17627/_/959017450/ ------------------------------------------------------------------------ To unsubscribe, send mail to lojban-unsubscribe@onelist.com