David Duffy escreveu:
> Isaac Marino Bavaresco wrote:
>   =

>> 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.
>>   =

>>     =

>
> Thank you to everyone for their input so far. In some ways, I'm now =

> feeling that C may be a waste of time since I already program in =

> assembler. What are the advantages of moving to C?
>   =


Suppose an if/else sequence with several complex expressions. In
assembly you would need to deal with lots of gotos, labels and all the
internals of the expressions themselves.

In C, you could write each expression in one line, with a more math-like
syntax (easier to understand at first glance than a long sequence of
instructions). You could use indentation also (not that you can=B4t use it
in assembly, but it is more awkward). Multi-byte values are treated
exactly as single-byte ones (in assembly, multi-byte operations take
much more source code lines to be written).

> Going back to the project that prompted all this; does it sound =

> reasonable to write assembly code for accessing an SD card and dealing =

> with the FAT?
> David...
>   =


There are several free/open-source packages to deal with FAT file
systems, all in C. I don=B4t know any in assembly.

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