On 31/05/2011 20:55, William Benson wrote:
>
>
>> Date: Tue, 31 May 2011 20:42:51 +0100
>> From: oli.glaser@talktalk.net
>> To: piclist@mit.edu
>> Subject: Re: [PIC] Introductory Book to C18?
>>
>> On 31/05/2011 20:33, William Benson wrote:
>>>>>   Date: Sun, 29 May 2011 00:12:55 +0100
>>>>>   From:oli.glaser@talktalk.net
>>>>>   To:piclist@mit.edu
>>>>>   Subject: Re: [PIC] Introductory Book to C18?
>>>>>   I would be wary of using the Microchip code in app notes for learni=
ng;
>>>>>   much of it is just basic functional examples to get you started, ra=
ther
>>>>>   than advice on how you should write the code.
>>> Where can you find a book "How you Write the CODE?" =09
>> I'm not sure what you mean here?
>>
> oli.glaser@talktalk.net said "I would be wary of using the Microchip code=
 in app notes for learning;                                        much of =
it is just basic functional examples to get you started, rather            =
                             than advice on how you should write the code."
> It looks like it trying to say, the way you write the CODE is the most im=
portant the basic code itself?  But not sure what you mean either?  That wh=
y I was asking?
> BEN  		 	   	=09

Ah I see.
If I understand you correctly, I didn't mean that the way the code=20
"looks" or the style is more important than what it does, no.
What I meant by "write the code" was how you should structure and=20
perform certain tasks efficiently.
For example, there is often several ways to do the same thing, but some=20
ways will be "better" than others as they will be easier to=20
read/change/port and so on.

What I was getting at is a lot of the example code in many app notes is=20
an "isolated" example just to get the point across.
They are not usually concentrating on the code itself, (i.e. whether it=20
could be easily changed, ported, how efficient it is) rather the idea=20
behind it. There will probably be an assumption that you are competent=20
in C and often little explanation of why certain constructs are used or=20
alternative options.
This is why I would say it would be better to learn from a book=20
dedicated to learning good coding practices, that goes into great detail=20
on these things.
I know it's badly explained (rushing) but I hope that makes some sense

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