| ??? 04/02/01 07:25 Read: times |
#10465 - RE: Too many falg bits in the code |
Hi Andy,
Naming the flags is like you name your children. Whatever you name them they would remain same so would their functions in the life. You name them to distinguish William from Adams........... Naming the flags is only to increase the legibility in the software facilitating the programer to conveniently organize the decisions based on the states. It would work as effeciently even if you don't define and name flags at the top of the code, just setting, clearing and testing with their hex address names. But then it will spin the programers mind...... However, not defining them at the top would a bit reduce the code size. Simon |
| Topic | Author | Date |
| Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many flag bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
RE: Too many falg bits in the code | 01/01/70 00:00 |