| ??? 08/24/06 21:54 Read: times |
#122970 - Going back and looking... Responding to: ???'s previous message |
Andy Neil said:
Go back and take a look and ask yourself what syntax error a spurious semicolon might cause. That would be instructive. #define SW1 P2_4; produces: C:/PROGRA~1/SDCC/JonTest.c(74):syntax error:token -> '=';column 14 among others where SW1 was referenced Where line 74 is: SW1 = 0; and nothing is in column 14 the ; is column 11 Wasn't very instructive for me, but what do I know about C, not much just learning. Jon |
| Topic | Author | Date |
| SDCC Nooby Question | 01/01/70 00:00 | |
| Ok got it | 01/01/70 00:00 | |
| it\'s ok in Keil | 01/01/70 00:00 | |
| Yes... | 01/01/70 00:00 | |
| The reason is... | 01/01/70 00:00 | |
| C first | 01/01/70 00:00 | |
| Learning C | 01/01/70 00:00 | |
| if this is cut and paste then | 01/01/70 00:00 | |
| Semi-colon was it | 01/01/70 00:00 | |
| C is fidgety about error declaration | 01/01/70 00:00 | |
| Syntax error | 01/01/70 00:00 | |
| Going back and looking... | 01/01/70 00:00 | |
| It means | 01/01/70 00:00 | |
| Preprocessor output | 01/01/70 00:00 | |
| explanation | 01/01/70 00:00 | |
| Semicolon | 01/01/70 00:00 | |
| yes, Andy you are absolutely correct | 01/01/70 00:00 | |
| Semicolon - example | 01/01/70 00:00 | |
| backwards | 01/01/70 00:00 | |
| HUH? | 01/01/70 00:00 | |
| try this | 01/01/70 00:00 | |
| Dallas app notes | 01/01/70 00:00 | |
| False economy | 01/01/70 00:00 | |
| OK | 01/01/70 00:00 | |
| Learning from the tools | 01/01/70 00:00 | |
| #define and the preprocessor | 01/01/70 00:00 | |
| are you sure? | 01/01/70 00:00 | |
Yes! | 01/01/70 00:00 | |
| Hmmm... | 01/01/70 00:00 | |
| SDCC Manual | 01/01/70 00:00 | |
| Err... ya think? | 01/01/70 00:00 | |
| Looks clear enough to me | 01/01/70 00:00 |