| ??? 06/07/10 07:14 Read: times |
#176464 - Another key sentence for any form of debugging Responding to: ???'s previous message |
My emphasis, again:
John Regehr said:
If your code needs volatile and you don’t understand why, this is probably what is happening. Far better to actually fix the problem than to rely on a hack you do not understand to solve a problem you do not understand.
http://blog.regehr.org/archives/28 On this forum (and similar), it is not uncommon to read something like, "I changed X and it fixed (sic) my problem - but I don't know why" As illustrated in the quote above, if you don't understand why the "fix" worked (sic), then you really shouldn't regard it as a fix - it may well just be masking symptoms... This is equally applicable to both hardware and software issues. |
| Topic | Author | Date |
| How to break your code with 'volatile' | 01/01/70 00:00 | |
| and for those, who prefer Slovak to English... | 01/01/70 00:00 | |
| A recommended read. | 01/01/70 00:00 | |
| Key sentence | 01/01/70 00:00 | |
Another key sentence for any form of debugging | 01/01/70 00:00 |