| ??? 03/30/01 23:18 Read: times |
#10438 - RE: Too many falg bits in the code |
Personally, I like to avoid calling variables "..._flag"
instead, give them names which immediately show the meaning of the flag; eg: in_menu BIT 40h ; bit is set when in the menu, cleared when not in the menu then the tests become more readable too; eg, if( in_menu ) |
| 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 |



