> You could say the same for C. The whole point is to hide the low level
> stuff generated by the compiler. All I'm saying is, personally, I need
> to know what's being hidden so I can truly understand what's going on.

That is where not playing with an FPGA at this stage is what you should be =
doing, and getting a feel for 'general' electronics and programming first. =
In some ways I feel you are attempting to put the cart before the horse.

Think in terms of pulling on the door handle of a car, to open the door. Yo=
u don't need to understand how the this lever pulls that arm against this s=
pring to rotate the other gizmo to unlatch the door - you have faith in the=
 higher level workings that pulling the handle unlatches the door. You shou=
ld get to a point where you have faith in the tools you are using to treat =
them as the same sort of black box producing the end result you want. You n=
eed some degree of knowledge about the tool (you pull on the handle, not ro=
tate it) to make the tool work, but you only need the inner understanding w=
hen things go wrong. But often you don't need a lot of understanding (squir=
t some WD40 into the lock to unjam it) to sort out a problem, or some advic=
e from others (such as you have been getting here on this thread) and go fr=
om there.
--=20
Scanned by iCritical.

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