??? 07/19/06 16:46 Read: times |
#120607 - each line of code must be justified Responding to: ???'s previous message |
The comment is a place for that justification. Erik's comment is quite correct.
The lines, the presence of which is assumed to be perfectly understandable, are often the ones that contain the ellusive oversight. If there's a comment, then one should be able to "see" how the comment ties into the code. Whenever there's a question, it warrants investigation, and that's how you find where the code and the comments really don't mean the same thing. RE |
Topic | Author | Date |
hex key pad code not working | 01/01/70 00:00 | |
Explanation | 01/01/70 00:00 | |
what, how | 01/01/70 00:00 | |
each line of code must be justified | 01/01/70 00:00 | |
correction made, still not workin | 01/01/70 00:00 | |
Lookup table | 01/01/70 00:00 | |
hyperlink | 01/01/70 00:00 | |
of course not, | 01/01/70 00:00 | |
shall I spoil the fun? | 01/01/70 00:00 | |
code workin partially | 01/01/70 00:00 | |
be specific | 01/01/70 00:00 | |
specific | 01/01/70 00:00 | |
check it in the simulator | 01/01/70 00:00 | |
Use serial port for debugging | 01/01/70 00:00 | |
confidence | 01/01/70 00:00 | |
I wouldn't do that | 01/01/70 00:00 | |
problem with find_num subroutine? | 01/01/70 00:00 | |
Code presentation | 01/01/70 00:00 | |
sorry it's 'hyper terminal' | 01/01/70 00:00 | |
Problem solved | 01/01/70 00:00 | |
which conclusion, please tell | 01/01/70 00:00 | |
Problem is NOT solved. | 01/01/70 00:00 | |
Post the solution please | 01/01/70 00:00 | |
solution | 01/01/70 00:00 | |
a 'killer solution' | 01/01/70 00:00 | |
killer???? | 01/01/70 00:00 | |
you 'eat' the main![]() | 01/01/70 00:00 |