Jeff Stevens wrote: > Yes, my focus is more on the specifics of C18 than the chip itself. > The PIC18 is so similar to the PIC16 and microchip's data sheets are > specific to the point of repetitiveness. As a result of your urging > to go back to the C18 manual, I actually printed it out to make it a > bit more useful. =20 I never actually used C18, but from what it seems, the manual is more of a reference. For me, the electronic form of references is much more useful, mostly because of searching -- that's what I do most with references. > No different than referring to Harbison and Steele for standard C. =20 I don't know Harbinson and Steele, but if it's too much of a reference manual, there is a large number of (generic) introductory material about the language C itself (without focus on C18). I still think that Kernighan and Ritchie provide everything you need to know about C (besides the reference of your specific compiler -- which you have -- and of course the language standard -- which you may also want to have). > They book I'm looking for is something like a bunch of application > notes, I'm sure there is a bunch of Microchip app notes that uses C18 and contain C18 code. > stylistic samples,=20 I wouldn't trust Microchip with this, and this is also nothing specific to C18. C language style is independent of the target system, and embedded projects for small processors in C look the same (in terms of style) no matter for which processor you write. > and explanations of how to do a few of the things that seem so trivial > in assembler but have no obvious solution in C18. Like what? There's always inline assembly if you really need it. All in all, it seems there isn't much C18 specific in your questions. You may get better answers by either widening your scope (C in (small) embedded systems) or restricting it (how to do something specific in C18). Gerhard --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .