On Sat, 4 Mar 2000, Matthew D Moss wrote:

> 
> The basic answer to this make sure you #include "pilot.h" only once.  How?
> Here's one basic method.  Create a file named "mypilot.h" which contains the
> following:
> 
> #ifndef __PILOT_H__
> #include <Pilot.h>
> #endif
> 
> (I think that's the correct symbol.)  Then in your source, #include
> "mypilot.h" and you should be okay.
> 

Yeah, I tried using that.  The problem that I come up with is that as soon
as I switch all of my files to using mypilot.h  Invariably one of them
starts acting like it can't see pilot.h. (It has no idea what a FrmPtr is
and similar things.)  Maybe I don't understand this, but I though that the
only way Pilot.h wouldn't be loaded was if the ocmpiler had already loaded
it.  If the compiler had already loaded it, then it should know what the
heck a FrmPtr is.  Hmmm.  what do you think I'm doing wrong.



> 
> On a side note, this question is asked so so so so often.  Is there a FAQ?
> Is this in it?  And if there is a FAQ, can a URL be added to the
> mailing-list signature so we have a constant reminder of where it is?
> 

I second that. :->

Noah

> ---- --- -- -
> Matthew D Moss
> [EMAIL PROTECTED]
> 
> 
> 
> 
> -- 
> For information on using the Palm Developer Forums, or to unsubscribe, please see 
>http://www.palm.com/devzone/mailinglists.html
> 

--------------------------------------------------------------------------------
Noah J. Ternullo                                [EMAIL PROTECTED]
--------------------------------------------------------------------------------
"As a matter of constitutional tradition, in the absence of evidence to the 
contrary, we presume that governmental regulation of the content of speech
is more likely to interfere with the free exchange of ideas than to
encourage it."                  - Supreme Court Justice John Paul Stevens 
--------------------------------------------------------------------------------


-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palm.com/devzone/mailinglists.html

Reply via email to