From lojban+bncCLr6ktCfBBCV7bbpBBoEN1qtKg@googlegroups.com Wed Jan 12 06:11:48 2011 Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1Pd1QO-000325-3S; Wed, 12 Jan 2011 06:11:48 -0800 Received: by gyb11 with SMTP id 11sf456499gyb.16 for ; Wed, 12 Jan 2011 06:11:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:x-beenthere:received-spf:date:from:to:subject :message-id:mail-followup-to:mime-version:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-disposition; bh=qcZGA3HcXVYidvEJBGu4JburMAthl+pjdI+dvQaLPmw=; b=v3aQWAfrPXjxwRogbI4nId8199j6I1M0Ys0sSSPXX1qZtgHW4/cNSWve2tn54TpGSE RNPA405rKN0kN0ZKQXQTuA/be2tTLi9qGEUS0AjYpQ34ikOpN7Wss6rMGXVNO5MW/pJ5 JeeZECWyTqxVgEiivkb+b+NUYoJeHFasuf5HI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:date:from:to:subject:message-id :mail-followup-to:mime-version:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-disposition; b=fFzl7sxkWmvJ+7fZ/dQnYNaX80gjaYqs53wa4nlpGJbGomJEMY06kflsrFkDwzgBXm 95kU2HzT7mt1hPM21yJ+dYkdVzogsHXF3qZxFDQo77dheQCowE7Ax3T2hTKxkvs7lp+3 wJFXmLe8Gk/A6lXp7fihhi+HBRLD96OJ2eWo0= Received: by 10.91.45.21 with SMTP id x21mr110302agj.23.1294841493147; Wed, 12 Jan 2011 06:11:33 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.150.143.13 with SMTP id q13ls458957ybd.5.p; Wed, 12 Jan 2011 06:11:32 -0800 (PST) Received: by 10.236.110.35 with SMTP id t23mr197272yhg.14.1294841492549; Wed, 12 Jan 2011 06:11:32 -0800 (PST) Received: by 10.236.110.35 with SMTP id t23mr197270yhg.14.1294841492479; Wed, 12 Jan 2011 06:11:32 -0800 (PST) Received: from mail-gx0-f179.google.com (mail-gx0-f179.google.com [209.85.161.179]) by gmr-mx.google.com with ESMTP id j39si71287yhb.15.2011.01.12.06.11.32; Wed, 12 Jan 2011 06:11:32 -0800 (PST) Received-SPF: neutral (google.com: 209.85.161.179 is neither permitted nor denied by best guess record for domain of alanpost@sunflowerriver.org) client-ip=209.85.161.179; Received: by gxk21 with SMTP id 21so279538gxk.24 for ; Wed, 12 Jan 2011 06:11:32 -0800 (PST) Received: by 10.151.47.3 with SMTP id z3mr1954701ybj.131.1294841490640; Wed, 12 Jan 2011 06:11:30 -0800 (PST) Received: from sunflowerriver.org (c-68-35-167-179.hsd1.nm.comcast.net [68.35.167.179]) by mx.google.com with ESMTPS id f13sm430313yhf.33.2011.01.12.06.11.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 06:11:29 -0800 (PST) Date: Wed, 12 Jan 2011 07:11:24 -0700 From: ".alyn.post." To: Lojban List Subject: [lojban] any-word-SA-handling clarification Message-ID: <20110112141124.GA866@alice.local> Mail-Followup-To: Lojban List Mime-Version: 1.0 X-Original-Sender: alyn.post@lodockikumazvati.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.161.179 is neither permitted nor denied by best guess record for domain of alanpost@sunflowerriver.org) smtp.mail=alanpost@sunflowerriver.org Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline The Lojban PEG grammar has the following production: any-word-SA-handling <- BRIVLA-pre / known-cmavo-SA / !known-cmavo-pre CMAVO-pre / CMENE-pre This is the only production which uses known-cmavo-SA, known-cmavo-pre, and CMAVO-pre. I'm trying to determine how these productions interact, but these rules intersect the morphology interface in camxes, and I would appreciate help understanding them. known-cmavo-SA includes a *-pre rule for every selma'o. It doesn't include a rule for CMAVO-pre, hich would match any cmavo not classified into a selma'o by the morphology (like la'oi). To follow one path, pretend we're matching "a" when we get to the any-word-SA-handling production: known-cmavo-SA -> A-pre -> A -> A-word-pre known-cmavo-pre -> A-word-pre known-cmavo-SA matches through a slightly different route, but the only difference happens in the morphology interface section, and I'm confused over whether this is a substantive difference or not. It *seems* like known-cmavo-SA and known-cmave-pre are matching the same thing, if not literaly, then conceptually, or perhaps it is that they *should* be matching the same thing? If this is true, I understand the any-word-SA-handling to be slightly redundant: * if know-cmavo-SA doesn't match, then by definition the !known-cmavo-pre production *will* match (because of the ! operator), and if we have a cmavo not classified by selma'o (i.e., la'oi), it will be matched by the CMAVO-pre rule. If this is true, can these rules be folded together, say by deleting known-cmavo-pre and the single reference to it? I can think of a couple other ways to order the rules for the same effect, but the issue is the same: what is known-cmavo-pre doing that is different from known-cmavo-SA? -Alan -- .i ko djuno fi le do sevzi -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en.