This is not simply a case of a bug that did not get fixed. It is also a case
of code which did not fulfill the specification doc (the app note). Bugs I
could accept, after who has not left more than one in 'finished code'.
(though the apparent bug in this case means that the system could not
operate as specified)

The fact that this is published by the manufacturers of the devices makes
it, to me at least, even more annoying & leaves me skeptical of any other
app notes. As someone else said they are great sources of ideas, but having
seen this particular app note, I wonder how many of these ideas will work
without significant rework.....

Anyhow when I get a couple of more things sorted with this one, I'll put it
up for others to use.

Joe

-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
Harold Hallikainen
Sent: 31 May 2005 19:39
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] Microchip app notes quality. (Long grumble)


A problem with writing code then moving on is that bugs never get fixed. In
a production environment, we update code as production test and customers
find problems. I think an ap note tends to be written, published, then never
looked at again. The code pages at http://www.piclist.org are great since
users can add comments. It might be kinda interesting to have a pic code
wiki or CVS where users can contribute code, other users can comment on it,
remove bugs, make improvements, etc.

Harold


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


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