Mercurial > hg > toybox
comparison www/design.html @ 694:786841fdb1e0
Reindent to two spaces per level. Remove vi: directives that haven't worked right in years (ubuntu broke its' vim implementation). Remove trailing spaces. Add/remove blank lines. Re-wordwrap in places. Update documentation with new coding style.
The actual code should be the same afterward, this is just cosmetic refactoring.
| author | Rob Landley <rob@landley.net> |
|---|---|
| date | Tue, 13 Nov 2012 17:14:08 -0600 |
| parents | e6acd7fbbfee |
| children | 6083bc6005a2 |
comparison
equal
deleted
inserted
replaced
| 693:4a5a250e0633 | 694:786841fdb1e0 |
|---|---|
| 69 RAM (and making the disk seek is 10x slower than sequential reads/writes), | 69 RAM (and making the disk seek is 10x slower than sequential reads/writes), |
| 70 but it's just as true that a loop which stays in L1 cache is many times faster | 70 but it's just as true that a loop which stays in L1 cache is many times faster |
| 71 than a loop that has to wait for a DRAM fetch on each iteration. Don't worry | 71 than a loop that has to wait for a DRAM fetch on each iteration. Don't worry |
| 72 about whether "&" is faster than "%" until your executable loop stays in L1 | 72 about whether "&" is faster than "%" until your executable loop stays in L1 |
| 73 cache and the data access is fetching cache lines intelligently. (To | 73 cache and the data access is fetching cache lines intelligently. (To |
| 74 understand DRAM, L1, and L2 cache, read Hannibal's marvelous ram guid at Ars | 74 understand DRAM, L1, and L2 cache, read Hannibal's marvelous ram guide at Ars |
| 75 Technica: | 75 Technica: |
| 76 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part1-2.html>part one</a>, | 76 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part1-2.html>part one</a>, |
| 77 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part2-1.html>part two</a>, | 77 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part2-1.html>part two</a>, |
| 78 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part3-1.html>part three</a>, | 78 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part3-1.html>part three</a>, |
| 79 plus this | 79 plus this |
| 275 <p>The help text might someday have translated versions, and strerror() | 275 <p>The help text might someday have translated versions, and strerror() |
| 276 messages produced by perror_exit() and friends can be expected to be | 276 messages produced by perror_exit() and friends can be expected to be |
| 277 localized by libc. Our error functions also prepend the command name, | 277 localized by libc. Our error functions also prepend the command name, |
| 278 which non-english speakers can presumably recognize already.</p> | 278 which non-english speakers can presumably recognize already.</p> |
| 279 | 279 |
| 280 <p>An enventual goal is UTF-8 support, although it isn't a priority for the | 280 <p>An enventual goal is <a href=http://yarchive.net/comp/linux/utf8.html>UTF-8</a> support, although it isn't a priority for the |
| 281 first pass of each command. (All commands should at least be 8-bit clean.)</p> | 281 first pass of each command. (All commands should at least be 8-bit clean.)</p> |
| 282 | 282 |
| 283 <p>Locale support isn't currently a goal; that's a presentation layer issue, | 283 <p>Locale support isn't currently a goal; that's a presentation layer issue, |
| 284 X11 or Dalvik's problem.</p> | 284 X11 or Dalvik's problem.</p> |
| 285 | 285 |