R. Clayton (rclayton@monmouth.edu)
(no date)
Can I use your previous solution concept of passing a function, and a pointer
to the structure to the disk driver along with other variables needed to
complete IO operation, so that disk driver invokes the function after
completion of IO operation? Because this method seems to be a convenient way of
storing status and disk block number in process’s registers which was
blocked for completion of IO operation. Or will it become copying your logic?
You're certainly welcome to copy the design and the logic; that's why I make
the solutions available: I want you to learn new and interesting design and
logic. However, it's important that you not copy the code, because that's
what I consider cheating: you're not learning anything, but merely developing
your cut 'n' past hand-eye coordination.
How can you tell if you've crossed over from leaning new and interesting
design and logic and gone to cheating? Here's two simple tests (which are
among the ones that I use if I suspect cheating):
1 Have a friend point to random sections of your code. If you can give a
concise and correct explanation of what the code does, then you've learned
new and interesting design and logic. If you can't explain what the code
does, or you explain it incorrectly, you've cheated.
2 Have a friend randomly call out the name of procedures defined in your
code. Using nothing but a pencil and paper, you should be able to write
down a reasonable facsimile of the procedure's implementation. If you
can, then you've learned new and interesting design and logic. If you
can't, then you've cheated.
I'll be looking for (among other things) code that has a suspiciously
different from your previous work and is suspiciously similar to my own work.
If I find such things, I'll starting thinking seriously about potential
cheating.
This archive was generated by hypermail 2.0b3 on Fri Aug 23 2002 - 19:30:04 EDT