Re: About "set bits"

[Thien-Thi Nguyen <ttn@gnuvola.org>]

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

() Barry Margolin <barmar@alum.mit.edu>
() Thu, 11 Apr 2013 11:19:54 -0400

   True, these phrases can be ambiguous. But often the context and
   examples help quite a bit in figuring out the intent. In this case,
   there were a couple of examples; "bits" tells you to think in binary,
   and if you examined the binary values of the examples it should
   quickly become apparent what was meant.

Yes, i think if OP were to try more stuff in *scratch*, such questions
could be avoided.  In this case, i wrote examples that (to me) seem easy
to inspect and mentally verify, so that *scratch* is not even necessary.

(Although probably they could use some additional bit-field diagrams:

   1
   5      8 7      0
  ┌────────┬────────┐
  │00101000│00011100│  =>  (2 3 4 11 13)
  └────────┴────────┘
      28       1C

and

   1
   5      8 7      0
  ┌────────┬────────┐
  │00011100│00101000│  =>  (3 5 10 11 12)
  └────────┴────────┘
      1C       28

Let's hope people will step forward and improve the docs over time.)

-- 
Thien-Thi Nguyen
GPG key: 4C807502

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]