 |
| #2011 | | 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.
|
|
| #2012 | | Nearly every complex solution to a programming problem that I
have looked at carefully has turned out to be wrong.
-- Brent Welch
|
|
| #2013 | | Never make anything simple and efficient when a way can be found to
make it complex and wonderful.
|
|
| #2014 | | Never put off till run-time what you can do at compile-time.
-- D. Gries
|
|
| #2015 | | Never test for an error condition you don't know how to handle.
-- Steinbach
|
|
| #2016 | | Never trust a computer you can't repair yourself.
|
|
| #2017 | | Never trust an operating system.
|
|
| #2018 | | Never try to explain computers to a layman. It's easier to explain
sex to a virgin.
-- Robert Heinlein
(Note, however, that virgins tend to know a lot about computers.)
|
|
| #2019 | | Never underestimate the bandwidth of a station wagon full of tapes.
-- Dr. Warren Jackson, Director, UTCS
|
|
| #2020 | | New crypt. See /usr/news/crypt.
|
|
|
| ... ... |
