??? 04/24/06 14:02 Read: times Msg Score: +2 +2 Informative |
#114888 - absolutely correct! Responding to: ???'s previous message |
Yes, everyone who wants to take credit for producing code should be required to understand what it is required to do and how to do it. As more and more people are using 'C' to generate their code, acquiring code snippets from the internet has become a substitute for learning how to do it.
As a consequence I think it's appropritate that code posted on 8052.COM should ALWAYS contain one or two fatal errors designed to prevent its simple and direct use via cut-and-paste, and should be labelled as such. Example code should be functionally correct, but (a) impossible to compile without at least one grammar/syntax correction, and (b) useless without at least one logic correction. The flaws should be obvious to anyone who's understood the workings of (A) the language, (B) the requirements of the task, and (C) the details of the hardware involved. Consequently, the code snippets should be written in an intelligible form, using few of the esoterica commonly found in the typical "impenetrable" 'C' code. Preferably, application code on 8052.COM should be in ASSEMBLY LANGUAGE and not it 'C'. That way, 'C'-learners will be discouraged from pestering 8052.COM for their homework solutions. RE |
Topic | Author | Date |
Problem with lcd files | 01/01/70 00:00 | |
Definition | 01/01/70 00:00 | |
Yes | 01/01/70 00:00 | |
what files? | 01/01/70 00:00 | |
the link | 01/01/70 00:00 | |
Yes, the file has errors! | 01/01/70 00:00 | |
too lenient | 01/01/70 00:00 | |
Fines | 01/01/70 00:00 | |
that's the crux | 01/01/70 00:00 | |
interfacing a lcd in C | 01/01/70 00:00 | |
DIY? | 01/01/70 00:00 | |
absolutely correct! | 01/01/70 00:00 | |
I applaud but the last paragraph is hope | 01/01/70 00:00 | |
It could still be made to work | 01/01/70 00:00 | |
filtering | 01/01/70 00:00 | |
good idea + my 2ct | 01/01/70 00:00 | |
Good ideas | 01/01/70 00:00 | |
Richard, send me a ping![]() | 01/01/70 00:00 | |
where to find a code? | 01/01/70 00:00 | |
and rising! | 01/01/70 00:00 |