Playing with NASM
This commit is contained in:
parent
29d5f078a7
commit
96a39c9bbe
8 changed files with 15310 additions and 2 deletions
|
|
@ -358,7 +358,7 @@ The only other information I have about revision levels comes from a March 30, 1
|
|||
|
||||
However, that document does not indicate how a 80386-C0 part was marked, and I've found very little other
|
||||
information on the C0 stepping; it may have been quickly superseded by the D0 stepping, which used revision
|
||||
identifier 0x05.
|
||||
identifier 0x05. D1 and D2 steppings used identifier 0x08.
|
||||
|
||||
### Errata
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ However, don't use that technique to check for optional parameters:
|
|||
|
||||
if (!parameter) { ... }
|
||||
|
||||
because a valid numeric parameter could include 0, a valid string parameter could include "", etc.
|
||||
if a valid numeric parameter could include 0, or a valid string parameter could include "", etc.
|
||||
|
||||
Problems with type coercion are **NOT** problems caused by a poor choice of operators, so trying to make
|
||||
those problems go away by artificially limiting your choice of operators seems like the wrong solution.
|
||||
|
|
|
|||
Loading…
Reference in a new issue