Post by thread:[PIC]: RE: 16F84 first project "Mentor Needed"

> > If you start too big you'll never know if it's your code, the assembler > (tools), the programmer or the hardware you've designed. > Oh, that's not true. :) If there's anything we all learned, it's ALWAYS our code. (or maybe our hardware design) :) He who suspects the compiler first has a lot yet to learn. -Matt -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email spam_OUTlistservTakeThisOuTmitvma.mit.edu with SET PICList DIGEST in the body

>> He who suspects the compiler first has a lot yet to learn. He who suspects the compiler may have modified the compiler... I remember once I typed in a good part of an 8080 forth implementation from Kilobaud magazine. Then I ran it through the cross assembler (that I had written) and loaded it up into the 8085 simulator (that I had written) on the DEC mainframe. It didn't work... and I suddenly realized that I had FOUR probable sources of error, and three of them would be my fault! That's without counting improbable sources of error like errors in the assembler that the cross assembler had been written in... :-) BillW -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email .....listservKILLspam@spam@mitvma.mit.edu with SET PICList DIGEST in the body

> He who suspects the compiler first has a lot yet to learn. Yeah. I meant a bad workman always blames his tools, i.e. can't use them properly. Doh! Take me literally why not ;-)) It's no good writing the best code in the world if you cannot drive the tools to build it. I digress! Pete -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listservKILLspammitvma.mit.edu with SET PICList DIGEST in the body