From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: aditya siram Newsgroups: gmane.emacs.devel Subject: Re: [Ann]: An Implementation of the Shen programming language in Elisp and a call for help Date: Fri, 13 May 2016 20:11:07 -0500 Message-ID: References: <87futltpic.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c05435c43b5550532c313d6 X-Trace: ger.gmane.org 1463188323 19277 80.91.229.3 (14 May 2016 01:12:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 14 May 2016 01:12:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Alexis Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 14 03:11:58 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b1O7V-0005ql-Do for ged-emacs-devel@m.gmane.org; Sat, 14 May 2016 03:11:53 +0200 Original-Received: from localhost ([::1]:36329 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1O7U-0007ZR-R3 for ged-emacs-devel@m.gmane.org; Fri, 13 May 2016 21:11:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1O7R-0007Wt-Gs for emacs-devel@gnu.org; Fri, 13 May 2016 21:11:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b1O7P-0002tK-98 for emacs-devel@gnu.org; Fri, 13 May 2016 21:11:48 -0400 Original-Received: from mail-yw0-x235.google.com ([2607:f8b0:4002:c05::235]:33888) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1O7P-0002t9-2l for emacs-devel@gnu.org; Fri, 13 May 2016 21:11:47 -0400 Original-Received: by mail-yw0-x235.google.com with SMTP id j74so117955607ywg.1 for ; Fri, 13 May 2016 18:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lB3qLubxDKe/YuKTH0fCdH14Krilc16jn/3puDFdTnQ=; b=hliFUxiPnK4N4kvOaYQNEDLFvLvFRQDYfp1/EAp3ww1QYvCFQwsLEcxBtkd9jjoGbw Z7VXyQ4an7qC8fdOA0EK+9KKxyM23R8bX6Aq4I4m9WlLMILjv92JJvxFN1PqiYtQKlDt 0HWRcAkgVD7bAtZ/d2suwKLzOVmosZNEzzEOqCmV4rQnLGopGUKdbKIjusmPgTnIbTkZ tp/Z4tkIZRRDwe68p7Mc6V1qpLXlBVjslUb3VQJNaw1OUU/proTQJ+7sYEfJODU2dJzA EhAMIkdqYChXXZZNuFtIKqHMzphwLAe5YQ/I6QK0XkHNVekh74ncfjxtDWe9EnPGUkH4 cQFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lB3qLubxDKe/YuKTH0fCdH14Krilc16jn/3puDFdTnQ=; b=Vz8OfMLcC2CUIWI+RXBFr0I+7oDx5xhVLy7IUnzAD8e43WkDNadqUpePl9gmzZOahn fyoZmEhL+rUkkk0+QbbH7T5Wa/dZyuQOzjQDgLjfQaM7hgq9xZSmyG1wiNaaHT1mXFRH iJjEMoEBAB6FjDqcgPVvAij1oQigrPvjjGYscQu6t4Ud+TaoQd8ILd7t4Ff68YeZ8u48 HmCr63y53xeMG4X631rXV/DgVwvRtJPZ5J/nyiJEtC4UknT6wcBo+9+UAC11xM4WNytL cCQY7cfgN6v3CQ5r0WZvw3AZ3KLn41VUiNyV9j0J2uEMxJrdeBYllsELs0BH7RaRa4Ln PIDw== X-Gm-Message-State: AOPr4FUIJTBpqs4bmffdzU8uh7Z5HrUqYEE9U3gGJMB0yvdg/0UpABdwQjWkpHj/rRjxPTL0Jx/G5BM6aT2LyQ== X-Received: by 10.13.247.193 with SMTP id h184mr9700414ywf.225.1463188306763; Fri, 13 May 2016 18:11:46 -0700 (PDT) Original-Received: by 10.37.52.129 with HTTP; Fri, 13 May 2016 18:11:07 -0700 (PDT) In-Reply-To: <87futltpic.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4002:c05::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203836 Archived-At: --94eb2c05435c43b5550532c313d6 Content-Type: text/plain; charset=UTF-8 Hi, Thanks for taking the time to reply. This is generated code so I have less control over what is used. I thought disabling the warning up top would take care of it. -deech On Fri, May 13, 2016 at 8:08 PM, Alexis wrote: > > aditya siram writes: > > 1. I can't seem to get rid of warnings when byte-compiling the generated >> "shen.el" [4] even though I have the byte-compile-warnings property the top >> of the file. I'm getting a lot of "unused lexical variable" warnings even >> though "lexical" is in the list of warnings. >> > > Well, it seems you're not making use of the lexical variables you define. > For example: > > (shen/let NewHistory (shen/shen\.update_history > NewLineread History) (shen/let Parsed > (shen/fst NewLineread) (shen/shen\.toplevel > Parsed))))))) > > Here you create the `NewHistory' variable, but don't make use of it within > the scope of the `shen-let'. > > Similarly, there are things like: > > (shen/let Record (shen/shen\.record-source V13163 KL) > KL)))) > > where `Record` is not used within the relevant scope, and: > > (shen/let NewVector (shen/vector (shen/- > Limit 1)) (shen/shen\.tlv-help V14674 2 Limit > (shen/vector (shen/- Limit > 1)))))))) > > where `NewVector' is not used within the relevant scope, and so on. > > So, why are you binding variables you don't make any use of after the > initial binding? > > Alexis. > --94eb2c05435c43b5550532c313d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,
Thanks for taking the time to reply= . This is generated code so I have less control over what is used. I though= t disabling the warning up top would take care of it.
-deech

On Fri, May 1= 3, 2016 at 8:08 PM, Alexis <flexibeast@gmail.com> wrote:<= br>

aditya siram <aditya.siram@gmail.com> writes:

1. I can't seem to get rid of warnings when byte-compiling the generate= d "shen.el" [4] even though I have the byte-compile-warnings prop= erty the top of the file. I'm getting a lot of "unused lexical var= iable" warnings even though "lexical" is in the list of warn= ings.

 Well, it seems you're not making use of the lexical variables you defin= e. For example:

=C2=A0 =C2=A0(shen/let NewHistory=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 (shen/shen\.update_history NewLineread History)=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 (shen/let Parsed=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (shen/fst NewLineread)= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 (shen/shen\.toplevel Parsed)))))))

Here you create the `NewHistory' variable, but don't make use of it= within the scope of the `shen-let'.

Similarly, there are things like:

=C2=A0 =C2=A0(shen/let Record=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 (shen/shen\.record-source V13163 KL) KL))))

where `Record` is not used within the relevant scope, and:

=C2=A0 =C2=A0(shen/let NewVector=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 (shen/vector=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(= shen/- Limit 1))=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (shen/shen= \.tlv-help V14674 2 Limit=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0(shen/vector (shen/- Limit=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A01))))))))

where `NewVector' is not used within the relevant scope, and so on.

So, why are you binding variables you don't make any use of after the i= nitial binding?

Alexis.

--94eb2c05435c43b5550532c313d6--