David Duffy (AVD) escreveu:
> That's a good question Bob. To be honest, I'm confused about what I =

> really want / need in the way of a C compiler, what's free and what's not!
>
> I've just started reading an eBook on C (for PICs) and maybe it's not =

> all that different to Delphi (Pascal) after all. Sure the syntax is =

> different, but the overall idea seems to be much the same.
>
> I've always programmed in assembler. Perhaps it is really an inefficient =

> way (time wise) to do things, but I just program the way I know how.
>
> Projects that involve more complexity seem (to me) to be better suited =

> to C. Maybe not in reality. I really don't know. I'd just like to get =

> projects out the door with less low level programming these days.
> David...
>   =


If you don=B4t need to extract every bit of performance from the CPU, C is
much faster to program and get things running. Besides, it is easy to
port to different processors and maintain.

If you are building an engine controller, which needs cycle-exact loops
and timing, etc. then I would advise using assembly. For a calculator,
with lots of user interaction and complicated logic it is better to use
C, perhaps with some assembly routines for time intensive calculations.

Remember, you can always mix C and assembly. The complex and not
performance critical tasks may be done in C (eg.: user interface), and
the high-performance tasks in assembly.


Another thought: tasks that only may be done in assembly in one CPU,
sometimes can be done in C in a more powerful CPU.

Best regards,

Isaac

__________________________________________________
Fa=E7a liga=E7=F5es para outros computadores com o novo Yahoo! Messenger =

http://br.beta.messenger.yahoo.com/ =


-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist