From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Too many permutations computed
Date: Thu, 03 Aug 2023 18:08:09 +0200 [thread overview]
Message-ID: <873510kt1y.fsf@dataswamp.org> (raw)
In-Reply-To: A-X9qLuC1df5WXeaYQNcjNiEJC4H5Tnmkq-R-nwX-DHLCAX0lxj3leI3dC3lhbIsZNANSFwo0kHGt4Qqm3YbMUc13xv3bJH6GGG24cxQLHs=@proton.me
uzibalqa wrote:
>> (while (< j h) [...]
>> (setq j (1+ j)))
>> [...]
>> for i := 0; i < k-1; i += 1 do [...]
>
> Do you understand what the i += 1 does ? It is the same as
> i++, am I right ? The difference lies in the timing of when
> the increment takes place (immediately in the case of i +=
> 1, and after the value is used in the case of i++). Do you
> think the distinction mentioned makes a difference for the
> algorithm ?
It is up to the designer of the pseudo code to decide if it
works like that, if it does then it would make
a difference, yes.
See if you can write the Elisp as close as possible to the
pseudo code, including the variable names:
(cl-loop for i from 0 to ... )
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-08-03 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:45 Too many permutations computed uzibalqa
2023-08-02 10:13 ` Emanuel Berg
2023-08-03 15:42 ` uzibalqa
2023-08-03 16:49 ` uzibalqa
2023-08-03 22:13 ` Emanuel Berg
2023-08-04 18:44 ` Heime
2023-08-03 15:52 ` uzibalqa
2023-08-03 16:08 ` Emanuel Berg [this message]
2023-08-04 18:39 ` Heime
2023-08-03 18:23 ` tpeplt
2023-08-03 23:25 ` Emanuel Berg
2023-08-04 21:45 ` tpeplt
2023-08-06 13:32 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873510kt1y.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).