Timeline for Checking opcode values
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 21, 2014 at 0:55 | history | edited | user117529 | CC BY-SA 3.0 |
deleted 18 characters in body
|
| Mar 11, 2014 at 20:40 | comment | added | supercat |
This sort of design may be particularly good if the same sequence of tests is done in several methods, and each case has a semantic meaning [possibly explicit no-op]. For example, if the code selects a sequence of if statements based upon an operating mode, a command to "switch to XXX mode (if not already in that mode)" could be handled as a no-op in the XXX mode if-block, but perform an action for the if blocks associated with other modes.
|
|
| Mar 11, 2014 at 1:48 | review | First posts | |||
| Mar 11, 2014 at 2:00 | |||||
| Mar 11, 2014 at 1:32 | history | answered | user117529 | CC BY-SA 3.0 |