| ??? 10/21/02 22:49 Read: times |
#31173 - RE: best ways to bit operation in keil C |
"best way (optimize)"
"Optimum" is a subjective term! Do you mean: * Least code size? * Least data usage? * Fastest execution? * Easiest for the programmer to implement? * Easiest to maintain? * some combination of the above, or even something completely different. If you're doing extensive bit manipulation, you might find it advantageous to copy you data to a bit-addressable area (eg, BDATA), do the bit stuff there, then copy the result back. BTW: for "cheak" I presume you mean "check," as in "check if the bit is set"? |
| Topic | Author | Date |
| best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation to andy | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation to andy | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
| RE: best ways to bit operation in keil C | 01/01/70 00:00 | |
RE: best ways to bit operation in keil C | 01/01/70 00:00 |