From: Joel Reicher <joel.reicher@gmail.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: Heime <heimeborgia@protonmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: imenu rescan automatically
Date: Mon, 12 Aug 2024 23:02:01 +1000 [thread overview]
Message-ID: <868qx1zygm.fsf@gmail.com> (raw)
In-Reply-To: <trinity-6d67eef4-0bae-45ca-86bd-47d2e210dc57-1723465975795@3c-app-mailcom-bs11> (Christopher Dimech's message of "Mon, 12 Aug 2024 14:32:55 +0200")
Christopher Dimech <dimech@gmx.com> writes:
> So I can forget any useful code that words.
For code to work it 'only' requires that the series of state
changes executed by the machine leads to the desired final state.
It cannot and should not be underestimated how obfuscated that can
be, and it is orthogonal almost to the point of being irrelevant
to the way humans understand code.
An example from the UNIX fortune file:
n = ((n >> 1) & 0x55555555) | ((n << 1) & 0xaaaaaaaa);
n = ((n >> 2) & 0x33333333) | ((n << 2) & 0xcccccccc);
n = ((n >> 4) & 0x0f0f0f0f) | ((n << 4) & 0xf0f0f0f0);
n = ((n >> 8) & 0x00ff00ff) | ((n << 8) & 0xff00ff00);
n = ((n >> 16) & 0x0000ffff) | ((n << 16) & 0xffff0000);
-- C code which reverses the bits in a word.
If it works, but you don't understand it, it doesn't work.
Regards,
- Joel
prev parent reply other threads:[~2024-08-12 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 16:51 imenu rescan automatically Heime
2024-08-11 23:41 ` Joel Reicher
2024-08-12 9:34 ` Heime
2024-08-12 10:13 ` Joel Reicher
2024-08-12 10:21 ` Heime
2024-08-12 10:50 ` Joel Reicher
2024-08-12 11:27 ` Heime
2024-08-12 11:57 ` Joel Reicher
2024-08-12 12:14 ` Heime
2024-08-12 12:20 ` Joel Reicher
2024-08-12 12:32 ` Christopher Dimech
2024-08-12 13:02 ` Joel Reicher [this message]
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=868qx1zygm.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--cc=dimech@gmx.com \
--cc=heimeborgia@protonmail.com \
--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).