On Thu, May 5, 2011 at 10:54 AM, Michael Watterson wrot= e: > no you don't. Even on C on any CPU big enough to have a "mainstream" OS, > 99% of expertise is not even knowing C syntax, but C libraries. Unless > you are writing a device driver you don't want to know how it's > implemented. Even then what you "need to know" of what is "hidden" by > compiler is very little. I define necessity here in terms of my personal requirement to understand. Maybe it's just me, but I had a hard time explaining the concept of "returning" a value in C to a classmate who doesn't know what CPU registers and stacks are. In any case, after fiddling around with Verilog for a while, I finally got around to making something cool: http://pastebin.com/GLTueVuE It just counts the clock pulses in a register and displays them on an array of LEDs. At the same time, it drives a multiplexed 4-digit 7-segment display and displays any value you like. All written nicely and with modules instantiated and stuff. Finally getting the hang of this thing. Hardest thing so far was deciding whether identifiers should be registers or wires. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .