On Sun, Dec 07, 2008 at 07:30:14PM -0500, solarwind wrote:
> @Others:
> 
> That being said, almost all or 100% of the stuff I've asked can be
> found on google, but the thing about google is you have to KNOW what
> you're wanting to find and KNOW the right question to ask. I DON'T
> know the right question. That's where other humans come in - they
> interpret my questions and either tell me what the right question is,
> or simply paste some links or even explain the solution to me. This I
> am grateful for. It's not that I'm too lazy to google it, It's just
> that google doesn't always give you the right answers to your question
> and sometimes you don't know the right question to ask.
> 
> Please understand, I'm not doing this on purpose. I'm just trying to learn.

This argument has some validity. However, unless you provide context like
you have above, there's no way for responders to know that you've made the
effort.

The simple solution is to make the effort, then explain your confusion.
That way anyone responding will:

1) know that you have made the effort.
2) have a common starting point from where to start explaining.

The point is that it only takes you a minute or two to start the process
and at least some of the time, the answer that pops up in Google/Yahoo etc.
will be clear enough that you won't have to send out a message to the
nearly 2500 readers of this list, most of who will suggest that you look it
up on Google.

As aside: I know that you want to program in C. But you've already run into
the issue of programming PICS where knowing assembly will help you. I have
argued over the years that a saavy PIC developer should have at least a
reading level understanding of PIC assembly. The reason is that PIC
assembly is the common language of concepts discussion. As you already know
there are several C compilers for the PIC, and each has a different way of
referring to on chip resources. So unless someone is using the exact same
compiler as you are, it gets a bit muddled in terms of describing concepts.
I strongly suggest that you take the time to write at least a simple
project or two in PIC assembly just so that you can read it well enough so
that when someone points you to a resource, such as the MidRange Manual,
where all the examples are in PIC assembly, you can do what was suggested
and translate those examples into the language of your choice.

Hope this helps,

BAJ
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist