all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: master ac1d15e95c 1/2: ; * src/data.c (Fash): More precise doc string
Date: Tue, 19 Jul 2022 18:54:08 +0300	[thread overview]
Message-ID: <83r12hm733.fsf@gnu.org> (raw)
In-Reply-To: <E731A615-DE9B-40B3-B9EC-E484BB04E6E0@acm.org> (message from Mattias Engdegård on Tue, 19 Jul 2022 17:08:48 +0200)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 19 Jul 2022 17:08:48 +0200
> Cc: emacs-devel@gnu.org
> 
> 19 juli 2022 kl. 16.26 skrev Eli Zaretskii <eliz@gnu.org>:
> 
> >  . it requires the reader to understand that shifting, multiplication,
> >    and division are equivalent
> >  . it requires the reader to understand the notion of "rounding down"
> 
> You certainly don't think highly of elisp programmers...

That's besides the point.  Clear documentation should be
understandable by everyone.

> Shifting left one step multiplies the value by two.
> Shifting right one step divides the value by two, after first decrementing the value by one if it was odd.

Still not there, sorry.

It is okay to say that shifting is the same as multiplying or
dividing, but why say _only_ that?  The operation is "bit shift", so
the most natural way of describing it is in terms of shifting bits.
No?



  reply	other threads:[~2022-07-19 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 13:49 master ac1d15e95c 1/2: ; * src/data.c (Fash): More precise doc string Eli Zaretskii
2022-07-19 14:19 ` Mattias Engdegård
2022-07-19 14:26   ` Eli Zaretskii
2022-07-19 15:08     ` Mattias Engdegård
2022-07-19 15:54       ` Eli Zaretskii [this message]
2022-07-19 17:46         ` Mattias Engdegård
2022-07-19 19:04           ` Eli Zaretskii
2022-07-20  5:57         ` Richard Stallman
2022-07-19 16:29   ` 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=83r12hm733.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.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.