| ??? 10/08/09 10:51 Read: times |
#169527 - Isolate the code block, use cpp Responding to: ???'s previous message |
All you can do is selectively disable the code from each function, until the message disappears.
Re-enable this suspect block. Then run the pre-processor and examine what code the compiler is sent by this suspect block. From the message, you could look for typedef statements or variable declarators. Once you have found the culprit, express your intention in a more straightforward way. SDCC is fairly robust and should translate bog-standard C quite well. David. |
| Topic | Author | Date |
| SDCC Internal Error | 01/01/70 00:00 | |
| No mention of a source line number for the input file? | 01/01/70 00:00 | |
| NO | 01/01/70 00:00 | |
| You have broken SDCC? | 01/01/70 00:00 | |
| I've Searched SDCC forums | 01/01/70 00:00 | |
| May be I am the first to see this. | 01/01/70 00:00 | |
| 2.6.0? | 01/01/70 00:00 | |
| I tried with newest SDCC snapshot and submitted a bug | 01/01/70 00:00 | |
| Fixed | 01/01/70 00:00 | |
That's service for you! | 01/01/70 00:00 | |
| Got It!! | 01/01/70 00:00 | |
| Just main() is ancient C | 01/01/70 00:00 | |
| Isolate the code block, use cpp | 01/01/70 00:00 |