Bob Ammerman roadrunner.com> writes: >=20 > > compilers. I actually found that learning assembly to any functional=20 > > level > > takes too much time that I do not have. e.g. in 'C' one can type: > > printf("Hello, world\r\n"); >=20 > Yeah, but you better know that "printf" will take up several K of your=20 > limited code space. You are absolutely right, as usual. If I were to develop a real-time syste= m with us resolution, I would probably not use printf(). But I now have a 0.= 1 s real-time system, have 8 printf("%Ul\t", long) executing each 0.1 s; it run= s on 16F877A, uses about 50% of RAM (there are other things it does, not just pr= intf) and has enough idle time to handle more tasks. If I run out of space, I wi= ll just go to 18F and the problem is solved! >=20 > Knowing a bit of the under-the-hood stuff (not necessarily the assembly=20 > language) would leave you in a much better position to know that such thi= ngs=20 > will happen. Completely agree, and, since I started PICking on 16F84, I often find mysel= f trying to minimize the code only to realize that improvement is minimal in = terms of code size/execution time. But again, it is highly dependent on the type= of device. >=20 > BTW: Look at "puts()" as an alternative to "printf". If you need formatte= d=20 > values try things like "itoa()" or write your own simple formatting=20 > function. >=20 Thanks for the pointers to that, I will keep it in mind.=20 Sergey Dryga http:/beaglerobotics.com --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .