Use markdown style lists
This commit is contained in:
parent
2091516544
commit
307b59584f
17 changed files with 120 additions and 120 deletions
22
01-04.md
22
01-04.md
|
|
@ -105,17 +105,17 @@ whizzing through the data in the buffer inside a single loop.
|
|||
There are four reasons that many programmers would give for not trying
|
||||
to improve on Listing 1.4:
|
||||
|
||||
**1.** The code is already fast enough.
|
||||
|
||||
**2.** The code works, and some people are content with code that
|
||||
works, even when it's slow enough to be annoying.
|
||||
|
||||
**3.** The C library is written in optimized assembly, and it's likely
|
||||
to be faster than any code that the average programmer could write to
|
||||
perform essentially the same function.
|
||||
|
||||
**4.** The C library conveniently handles the buffering of file data,
|
||||
and it would be a nuisance to have to implement that capability.
|
||||
1. The code is already fast enough.
|
||||
|
||||
2. The code works, and some people are content with code that
|
||||
works, even when it's slow enough to be annoying.
|
||||
|
||||
3. The C library is written in optimized assembly, and it's likely
|
||||
to be faster than any code that the average programmer could write to
|
||||
perform essentially the same function.
|
||||
|
||||
4. The C library conveniently handles the buffering of file data,
|
||||
and it would be a nuisance to have to implement that capability.
|
||||
|
||||
I'll ignore the first reason, both because performance is no longer an
|
||||
issue if the code is fast enough and because the current application
|
||||
|
|
|
|||
Loading…
Reference in a new issue