Change bold code snippets to inline code blocks
This commit is contained in:
parent
f658bfbb40
commit
3c76d884ef
185 changed files with 1772 additions and 1772 deletions
6
16-07.md
6
16-07.md
|
|
@ -127,8 +127,8 @@ exactly that. They stepped back, thought about what the code actually
|
|||
needed to do, rather than just improving how it already worked, and
|
||||
implemented code that sprang from that new perspective.
|
||||
|
||||
You can see one example of this in Listing 16.6, where Willem uses **CMP
|
||||
AX,0101H** to check two bytes at once. While you might think of this as
|
||||
You can see one example of this in Listing 16.6, where Willem uses `CMP
|
||||
AX,0101H` to check two bytes at once. While you might think of this as
|
||||
nothing more than a doubling up of tests, it's a little more than that,
|
||||
especially when taken together with the use of two loops. This is a
|
||||
break with the serial nature of the C code, a recognition that word
|
||||
|
|
@ -157,7 +157,7 @@ non-word. A word is not a transition, it is the presence of a group of
|
|||
characters. Thought of this way, the code would have counted the word
|
||||
when it first detected the group. Had you done this, your main program
|
||||
would not have needed to look for the possible last transition or deal
|
||||
with the semantics of the value in **CharValue**."*
|
||||
with the semantics of the value in `CharValue`."*
|
||||
|
||||
John Richardson, of New York, contributed a good example of the benefits
|
||||
of a different perspective (in this case, a hardware perspective). John
|
||||
|
|
|
|||
Loading…
Reference in a new issue