>4) Ask yourself why others should spend their time looking through the
>large
>code segment you posted looking for bugs when you havn't even tried it on
>real
>hardware or a simulator and there may not be any bugs.

I don't mean to sound harsh, but I definitely agree with this opinion.  I
think you'll find that most people on this list are more than willing to
help out with a specific problem, because it's challenging and may offer
some reverse benefits to the people thinking about the problem and helping
solve it.  However, your comment of "take a look at this and let me know if
it will work before I test it" is not going to get people to look over 50+
lines of code that may or may not have errors.  Working through another
person's code is tough to do, especially if there is no real motivation to
do so.

Just as some general advice, write your code, test it, debug it, improve it,
test it again, debug it again, etc. a few times, and if you STILL have a bug
that you can't seem to fix, then post the SECTION of the code in question to
the list and I'm sure people will be more than willing to help you find your
error.

--Andrew

_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.