I interested too. I've worked for organizations that agreed upon naming
standards for types, global variable, subroutines, compilation units, etc.
on the one hand, and source files and header files on the other, such that
given the name of something from the first category, it was trivial to
figure out the name of something from the second (and vice versa). This led
to many files to manage, but that's what source code management tools are
for. As a result, it was much easier to understand code written by other
people, since you could quickly get to any piece of information you needed.
I wish Palm would do the same.
Mark Peters
----------
>From: John Marshall <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] (palmdev)
>Subject: Re: API Documentation - Determining Headers required ?
>Date: Tue, Jul 20, 1999, 8:57 AM
>
> I'm still interested in a survey of who would use separate headers instead
> of a Pilot.h all-or-nothing if they could. So far Roger and I are keen --
> anyone else?
>
> John
>
