| ??? 06/10/11 13:25 Read: times |
#182582 - and therefore ... Responding to: ???'s previous message |
Goto really is a bastard code construct
99.x% of places outlaw the goto. And therefore (being, probably the most comolicated thing to implement in a C compiler) the most likely instruction to be erroneously processed. chicken and egg. just think of the implementation of a construct like this here: a(); xxx a (xxx) { b(); xx b (xxx) ... goto here Erik |
| Topic | Author | Date |
| Compiler variations?? | 01/01/70 00:00 | |
| Fundamental philosophy of High-Level Languges (HLL) | 01/01/70 00:00 | |
| C code | 01/01/70 00:00 | |
| and so what | 01/01/70 00:00 | |
| Stop wondering about the compiler output | 01/01/70 00:00 | |
| Very nice to learn this important matter | 01/01/70 00:00 | |
| Exactly what you wrote | 01/01/70 00:00 | |
| volatile sbit may be the problem | 01/01/70 00:00 | |
| read up on (not) volatile | 01/01/70 00:00 | |
| Look at my profile | 01/01/70 00:00 | |
| Not offence intended | 01/01/70 00:00 | |
| defining P0_6 so that compiler doesn't treat it as volatile | 01/01/70 00:00 | |
| Skip the goto - almost always exists beautiful rewrites | 01/01/70 00:00 | |
| Goto really is a bastard code construct | 01/01/70 00:00 | |
| and therefore ... | 01/01/70 00:00 | |
Will come back with modified code | 01/01/70 00:00 | |
| Wonderful as always! | 01/01/70 00:00 |