At 5:28 PM -0700 1999/04/23, Kenneth Albanowski wrote:
>...My point is to ask whether the *Prv.h headers _are_
>intended to be useful for developers. If so, then all referenced
>structures need to be available. (And maybe the header oughn't to be
>called *Prv.h if it isn't.) If not, why are the *Prv.h headers available
>at all?
To help you debug... and that's about all, really.
>Of course, I rather assume this is all just a matter of happenstance, and
>the simple result of stripping out the non-public headers and leaving
>everything else. In which case, I'd just like to ask that the supplied
>*Prv.h headers be made fully functional, as a bug-fix to the supplied SDK.
Private headers will never be considered 'open for use' by developers. They're
private... that's the point. Thus we reserve the right to change anything and
everything in there, at any time, without warning. Because doing so won't break our
published, supported APIs.
BTW, there may very well be cases where the public APIs expose a dependency on a
private structure... if something like that turns up I'm sure we'll take some action
to correct the situation and keep the public API working for as long as we can (for
example, moving the structure into a public file... or something like that). So unless
otherwise noted, any *Prv.* file is ours alone to play with.
Heh heh heh... "Look, But Don't Touch."
Regards,
Jim Schram
3Com/Palm Computing
Partner Engineering
