Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
04/24/06 14:46
Read: times


 
#114892 - It could still be made to work
Responding to: ???'s previous message
Erik Malund said:
Richard: 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.
THAT will never happen, however much everybody wish so. It is even possible that one or more of the copy artists, as it is now, stumble on the C examples and thus do not even ask.


Yes, it's too much to hope for, but I see no problem with letting the "copy artists" flounder.

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.
I love that suggestion, but how many "'C'-learners will be pestering" with "where is tha fault, I need to turn in my paper tomorrow and do not have the time (read willingness/ability) to find it myself.


Those are the ones we want most to filter out, aren't they? If we simply beg the moderators to filter 'em out, i.e. not post those, won't that fix the problem? They should be obvious enough.

Then, of course, we have those that just have to brag by posting in response "I found the fault, it is...". I sometimes think those (presumably more capable) are worse by aiding and abetting than the (presumably less capable) copy artists asking for code.

Erik



Those should be "filterable" as well, don't you think? We don't have to defeat our own filters. If every code sample has a paragraph in it at the beginning and end, indicating that there are intentionally placed flaws, I don't think it will go unnoticed by even the most unsophisitcated cut-and-pasters.

OTOH, I think I'd like to be there when the instructor asks the cut-and-paster what those paragraphs mean.

RE






List of 20 messages in thread
TopicAuthorDate
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      

Back to Subject List