Received: from mail-la0-f62.google.com ([209.85.215.62]:32871) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Ym5BE-0004Mp-Ok; Sat, 25 Apr 2015 11:52:00 -0700 Received: by labgd6 with SMTP id gd6sf26841417lab.0; Sat, 25 Apr 2015 11:51:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type: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; bh=UFHpBDCyikrFE5BE36/1R1VYbpqIaen3dFa2ygaz1+k=; b=bkbly85QIhD37iXtJJl5o+/SdRxvy+DWn2YZjWmYYa8wYBr/EZAShvCdmMTd5boP4c sdZMETGk0OZwP6hg2hNbVQbo2ftRlZtwuG9pW18N5Gon77VzIjbjIyLOAh7PmvziyxL+ 4l8e/C4LBsUGW1SbkoJu2wxueEhvzJVwyo0o7h14f5XjPVk0llT/8Cp6ALr9nBZEycXo 5qTn8xdueZm1vfvTfyOgETISa+8m5u5PJfDLyjKekCXuKSiOb+01NY16OGAxZCgqOz2S 4u73eFyHjgpankHGWS9UUwaoOTuUpAlrDMlaPuU+i9OgXqloR/3eiVXMJ3Y3zapLpIer xEBg== X-Received: by 10.152.22.130 with SMTP id d2mr43250laf.7.1429987909354; Sat, 25 Apr 2015 11:51:49 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.152.29.36 with SMTP id g4ls625794lah.33.gmail; Sat, 25 Apr 2015 11:51:48 -0700 (PDT) X-Received: by 10.112.122.39 with SMTP id lp7mr2607343lbb.5.1429987908830; Sat, 25 Apr 2015 11:51:48 -0700 (PDT) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com. [2a00:1450:400c:c05::22c]) by gmr-mx.google.com with ESMTPS id m3si166971wia.1.2015.04.25.11.51.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Apr 2015 11:51:48 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22c as permitted sender) client-ip=2a00:1450:400c:c05::22c; Received: by mail-wi0-x22c.google.com with SMTP id k4so56765082wiz.1 for ; Sat, 25 Apr 2015 11:51:48 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.239.99 with SMTP id vr3mr8290998wjc.151.1429987908717; Sat, 25 Apr 2015 11:51:48 -0700 (PDT) Received: by 10.27.56.18 with HTTP; Sat, 25 Apr 2015 11:51:48 -0700 (PDT) In-Reply-To: References: <87a8631e-1155-4a74-a1c4-47c79a5fe96f@googlegroups.com> Date: Sat, 25 Apr 2015 15:51:48 -0300 Message-ID: Subject: Re: [bpfk] selma'o ZEhEI and PEG From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: bpfk-list@googlegroups.com Content-Type: multipart/alternative; boundary=001a11c1b74255108a05149101a3 X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::22c as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: X-Google-Group-Id: 972099695765 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - Content-Length: 4374 --001a11c1b74255108a05149101a3 Content-Type: text/plain; charset=UTF-8 On Sat, Apr 25, 2015 at 1:37 PM, Alex Burka wrote: > I tried to do this (delete ZEI, add {zei} and {ze'ei} to SI, and move SI > from post_clause to pre_clause) but I was unable to complete the last step > without introducing left recursion into the pre_clause rule. So it seems > easier said than done. I am not an expert in these dark corners of the PEG, > though. > Yes, the magic words section is quite tricky. I think what you need is to also replace pre_zei_bu with something like: pre_zei_bu: (BRIVLA / !BU !ZEI !SI !SA !SU !FAhO CMAVO) spaces? (or a list of all si-erasable selmaho, if you want to be able to identify the selmaho of the erased/modifier words). The left recursion occurs because the current pre_zei_bu is calling pre_clause, which now calls pre_zei_bu, which calls pre_clause, which calls pre_zei_bu, which calls pre_clause, and so on... You also need to remove SA_clause from si_clause for the same reason. I heven't bothered to think what it should be replaced with, since I'd like SA out of the grammar altogether, but it probably should be some sort of sa_clause_no_pre added to erasable_clause. mu'o mi'e xorxes -- You received this message because you are subscribed to the Google Groups "BPFK" group. To unsubscribe from this group and stop receiving emails from it, send an email to bpfk-list+unsubscribe@googlegroups.com. To post to this group, send email to bpfk-list@googlegroups.com. Visit this group at http://groups.google.com/group/bpfk-list. For more options, visit https://groups.google.com/d/optout. --001a11c1b74255108a05149101a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sat, Apr 25, 2015 at 1:37 PM, Alex Burka <durka42@gmail.com>= wrote:
I tried to do this (delete ZEI, add {zei} and {ze'ei} to SI, and= move SI from post_clause to pre_clause) but I was unable to complete the l= ast step without introducing left recursion into the pre_clause rule. So it= seems easier said than done. I am not an expert in these dark corners of t= he PEG, though.

Yes, the magic = words section is quite tricky. I think what you need is to also replace pre= _zei_bu with something like:

pre_zei_bu: (BRIVLA /= !BU !ZEI !SI !SA !SU !FAhO CMAVO) spaces?

(or= a list of all si-erasable selmaho, if you want to be able to identify the = selmaho of the erased/modifier words).
=C2=A0
The left = recursion occurs because the current pre_zei_bu is calling pre_clause, whic= h now calls pre_zei_bu, which calls pre_clause, which calls pre_zei_bu, whi= ch calls pre_clause, and so on...

You also need to= remove SA_clause from si_clause for the same reason. I heven't bothere= d to think what it should be replaced with, since I'd like SA out of th= e grammar altogether, but it probably should be some sort of sa_clause_no_p= re added to erasable_clause.

mu'o mi'e xor= xes

--
You received this message because you are subscribed to the Google Groups &= quot;BPFK" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bpfk-list= +unsubscribe@googlegroups.com.
To post to this group, send email to bpfk-list@googlegroups.com.
Visit this group at ht= tp://groups.google.com/group/bpfk-list.
For more options, visit http= s://groups.google.com/d/optout.
--001a11c1b74255108a05149101a3--