> -----Original Message-----
> From: Bob Ebert [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 26, 1999 2:33 PM
> To: [EMAIL PROTECTED]
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: PalmOS API change (Was: Re: VoidHand vs. Handle)
>
>
> At 11:08 AM -0700 10/26/99, Richard Hartman wrote:
> >Will your compatibility headers have FooPtr ?
>
> They will.
>
> >If so, will it be by typedef or #define ? (Note that the results
> >would not be the same...)
>
> What's better?
If the goal is compatibility "better" is whatever way
they used to be defined (which is, I believe, by typedef).
If the difference in using typedef or #define doesn't strike
you right away, consider this declaration:
FooPtr a, b, c;
first when
typedef Foo *FooPtr;
then when
#define FooPtr Foo *
and consider the impact on "b" and "c"...
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
