At 01:27 PM 10/20/2011, Peter Johansson wrote:

>My suggestion is that you learn C and assembly side-by-side.  Write
>all of your small sample programs in both C and assembly, and then
>compare the code the C compiler generates with your own code.
>Knowledge of just how your compiler does things can really help when
>stepping through your code in the debugger.
>
>Chances are you will probably wind up coding entirely in C,
>particularly if your compiler has a very good optimizer for your MCU,
>but the time spent learning assembly will be time well spent.

I've been deliberately staying out this discussion (I don't grok 'C',=20
so I code exclusively in Assembler), but I think that the above=20
advice is the best suggestion.

If you already code in 'C' for other processors, it should be a short=20
learning curve.

Great advice, Peter.

dwayne

--=20
Dwayne Reid   <dwayner@planet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
(780) 489-3199 voice          (780) 487-6397 fax
www.trinity-electronics.com
Custom Electronics Design and Manufacturing

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