>Then learn it.
OK, I will :-) Do you have any recommendations on how I should get started
(maybe a book you've found useful, or a website..)?
>You need to understand what goes on at the low level on
>these small resource limited systems, else you will be forever bumping into
>strange symptoms with little chance of figuring them out.
Makes sense.. I decided not to learn assembler, to jump right into
microcontroller programming using C because *I thought* assembly programming
was something of the past, something that was being phased out. Thank you
for correcting my line of thinking. If I take a time-out and learn assembler
now, it sounds like I'll be saving myself many headaches in the long run.
>If you think a compiler will just take care of everything for you, then you
frankly don't
>belong here. Go back to Java, web apps, or whatever, and leave tiny
systems
>to those willing to take the time to understand them.
I "think" that I'm a senior in high school, self-taught when it comes to
programming and electronics, with very little idea of what to do. I'm
learning as I go, and asking for help when I need it.
Nathan
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
