| ??? 01/17/11 18:53 Read: times |
#180655 - Another neat feature Responding to: ???'s previous message |
My biggest complaint with C is that it just does not check your memory. The programmer can make an array and just not use the allocated memory because of an OBOB (off by one bug) and walk all over memory. I wish that there could be an attachment that would predict or limit the use of the array. Simple bugs that could be made fool proof, but are not. |
| Topic | Author | Date |
| it just struck me, is this why RTOS 'need' is so prevalent? | 01/01/70 00:00 | |
| Two Camps Here | 01/01/70 00:00 | |
| Best Practice | 01/01/70 00:00 | |
| a similar discussion... | 01/01/70 00:00 | |
| I have always maintained the belief... | 01/01/70 00:00 | |
| "non-arbitrary" ? | 01/01/70 00:00 | |
| "Real" Processing exposed | 01/01/70 00:00 | |
| Too Specific | 01/01/70 00:00 | |
| sweeping generalisation | 01/01/70 00:00 | |
| RTOS are very useful | 01/01/70 00:00 | |
| I think this got away ... | 01/01/70 00:00 | |
| Blocking/nonblocking I/O | 01/01/70 00:00 | |
| Not The only reason | 01/01/70 00:00 | |
| I considered developer effort | 01/01/70 00:00 | |
| code generator | 01/01/70 00:00 | |
| Another neat feature | 01/01/70 00:00 | |
| there is such an attachment ... | 01/01/70 00:00 | |
| Lots of tools available | 01/01/70 00:00 | |
| not really | 01/01/70 00:00 | |
| Lots of C tools | 01/01/70 00:00 | |
| widespread | 01/01/70 00:00 | |
| Missed the point! | 01/01/70 00:00 | |
Ecosystem | 01/01/70 00:00 |