From: Stephen Berman <stephen.berman@gmx.net>
To: 66656@debbugs.gnu.org
Cc: lewcreary@cs.com
Subject: bug#66656: Bug reports
Date: Sat, 21 Oct 2023 00:06:55 +0200 [thread overview]
Message-ID: <877cnhhrsw.fsf@gmx.net> (raw)
In-Reply-To: <472007690.294115.1697838145836@mail.yahoo.com> (Lewis Creary via's message of "Fri, 20 Oct 2023 21:42:25 +0000 (UTC)")
On Fri, 20 Oct 2023 21:42:25 +0000 (UTC) Lewis Creary via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
[...]
> The main bug I'm reporting consists in the fact that recently, when I
> tried to test the lisp function displayed just below, I triggered the
> lisp error message "`let' bindings can have only one value-form", when
> it is clear from inspection of the let* form in question that no such
> bug exists. The let* form in question does have just one value-form,
> the lisp variable eight-powr-sum..
>
> (defun octal-to-dec (n)
> (let* ((oct-str {number-to-string n)
> (octal-digits (string-to-reverse-numlist oct-str))
> (oct-digit nil)
> (eight-powr-term-val 0)
> (eight-powr-sum 0)
> (indx 0)
> (while-nil-val (while (<= indx (length octal-digits))
> (setq oct-digit (nth indx octal-digits)
> eight-powr-term-val (* oct-digit (expt 8 indx))
> eight-powr-sum (+ eight-powr-sum eight-powr-term-val)
> indx (1+ index) ))) ) ; end of let-variables
> eight-powr-sum )))
The error is because the first let-binding binds `oct-str' to both
`{number-to-string' and `n'. I guess `{' is a typo for `(' and there
should also be a closing `)': `(oct-str (number-to-string n))'.
Steve Berman
next prev parent reply other threads:[~2023-10-20 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <472007690.294115.1697838145836.ref@mail.yahoo.com>
2023-10-20 21:42 ` bug#66656: Bug reports Lewis Creary via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20 22:06 ` Stephen Berman [this message]
2023-10-21 7:27 ` Eli Zaretskii
2023-12-22 14:57 ` Stefan Kangas
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=877cnhhrsw.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=66656@debbugs.gnu.org \
--cc=lewcreary@cs.com \
/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.