> And even more in a non-professional setup, which will in most cases > mean: using gcc, which has warnings for such probable mistakes. True, however, these kind of tools and warning settings you have got in the assembly language too. Also you guys said Olin made his asm extension (pre-processor) as he realized the need because of the weakness of the asm language. This is the same here: lint and other tools invented as realised weaknesses of the C and/or other HLL languages. Probably if we would like to get the most secure code we would need to go for much more strict languages, like ADA. Anyway guys, HLL is great, and also it is nice to see good code optimizers existing such as XCSB. I'll definitely will have a look at this and other compilers if I can improve my productivity or the reliability of the firmware in the near future. Thanks, Tamas On Mon, Mar 10, 2008 at 12:15 PM, wouter van ooijen wrote: > > This is actually one of the lesser used arguments in favor of > > C: the existence of such tools. Whenever we discuss how > > unsafe programming in C is, we should consider programming in > > C with the available tools. At least when talking about > > programming in a professional setup. > > And even more in a non-professional setup, which will in most cases > mean: using gcc, which has warnings for such probable mistakes. > > Wouter van Ooijen > > -- ------------------------------------------- > Van Ooijen Technische Informatica: www.voti.nl > consultancy, development, PICmicro products > docent Hogeschool van Utrecht: www.voti.nl/hvu > > > > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- Rudonix DoubleSaver Did You Know that DoubleSaver is Smaller and More Powerful FailSafe Device than Any Other You can Get? http://www.rudonix.com -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist