??? 01/02/11 17:49 Read: times |
#180400 - Re: one C book should do Responding to: ???'s previous message |
Erik Malund said:
One final word stick to the serially programmable chips making a programmer makes no sense these days.
Oh, absolutely! Going over the datasheets and app notes, I'm leaning heavily towards the Atmel 89C51ED2 chips - 64K of onboard Flash program memory, 2K of EEPROM, and all the other bells&whistles one could think of using. :) One thing that confuses me about the whole language debate - I understand that languages like C and Pascal are inherently more structure-oriented than BASIC... and as such, they force you to think about the structure of the program you're developing. But if you consider the structure from the outset, what does it really matter which higher-level language you decide to use? Personally, I tend to work up a flowchart of what I want to do first. (It's a hold-over from my high-school computer programming courses, where we had to work out all the details first - before committing the program to punch-cards... :-O ) At that point, it shouldn't matter whether I code in C, Pascal, BASIC, Forth, or Assembly. So languages like C and Pascal would be good for getting an unorganized programmer to learn how to organize programs properly... but if you're already organized, there wouldn't be any real difference. Would there...? :) |