From: Alexis <flexibeast@gmail.com>
To: aditya siram <aditya.siram@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [Ann]: An Implementation of the Shen programming language in Elisp and a call for help
Date: Sat, 14 May 2016 11:08:43 +1000 [thread overview]
Message-ID: <87futltpic.fsf@gmail.com> (raw)
In-Reply-To: <CAJrReyi7YiyjCELAu8hMNyhfuh9m6BgfH0fqYgtm04UWbjevwg@mail.gmail.com>
aditya siram <aditya.siram@gmail.com> 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.
next prev parent reply other threads:[~2016-05-14 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 21:01 [Ann]: An Implementation of the Shen programming language in Elisp and a call for help aditya siram
2016-05-14 1:08 ` Alexis [this message]
2016-05-14 1:11 ` aditya siram
2016-05-14 1:30 ` Alexis
2016-05-14 1:41 ` Michael Heerdegen
2016-05-14 13:29 ` Stefan Monnier
2016-05-16 17:54 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87futltpic.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=aditya.siram@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.