> 1) Does pilot.h include most all declarations that
> are necessary for an app?
It depends on the app. I've encountered some routines that are
prototyped in (or actually reside in, if they are macros) headers that
are NOT included by simply including pilot.h. Examples: IsAlpha,
IsDigit, MemDeref. FWIW, my approach is to start by just including
pilot.h, see what (if any) complaints I get from the compiler/linker,
then go grepping the header files to find the additional ones I need to
include.
> 2) Does including pilot.h instead of individual
> headers cause any waste or excess program size?
I would hope not. It's generally a Bad Thing for C header files to
*define* things (create storage for them). C header files are for
*declaring* things (letting the compiler know they exist). I can't make
any statement about C++. In my experience, including too many header
files simply slows down the compiler.
> 3) Is there a kind of a summary list of the headers
> and when they should be included? Or what they
> provide?
You can kind of figure it out on your own with Palm OS because they've
divided the OS into "managers", and each manager for the most part has
its own header file.
If I may tack a complaint of my own onto this: there are useful macros
in the headers that are not documented in the Reference document (not
that I can find, anyway). Example: IsAlpha, IsDigit.
--
Roger Chaplin
<[EMAIL PROTECTED]>
