On Fri, 23 Apr 1999 [EMAIL PROTECTED] wrote:
> >I have to agree that it's a bit dodgy to have the supplied headers contain
> >references to structures that aren't supplied. Never mind what the
> >structures are for, without their size, you might as well forget about
> >using the containing structure. And if you _want_ people to forget about
> >using the containing structures, you might as well say that outright,
> >instead of leading them on a bit.
>
>
> The data structure in question is in a *Prv.h file, and requires that the
> user #define NON_PORTABLE before it can be used. Given those indicators, I
> don't think Palm is leading people on into believing that they can and/or
> should use the information within that file.
It's still the case that the header, Prv or not, NON_PORTABLE or not, is
basically useless. 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?
(Now, all of that is a bit strong. Everything else in such a header can be
quite useful, and all items in a structure before the undeclared structure
will be usable, and it's probably possible to guess the size of the
undefined structure in some cases. I certainly wouldn't want to see the
*Prv.h headers needlessly retracted in a future SDK, I've made far too
much use of them myself.)
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.
--
Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
