On 2008/11/17 00:47, "Matthew W. S. Bell" <[EMAIL PROTECTED]> wrote:
> On Sun, 2008-11-16 at 19:13 +0100, Max Kellermann wrote:
> > There is no documentation on that issue in the Debian package - no
> > README.Debian, and no documentation in the patch file.  Would you mind
> > to add it?
> 
> Other than adding a note to README.Debian that a patch has been added
> that makes the public headers and internal implementation of libfaad
> consistent, what documentation would you like? (The provided libfaad
> headers are canonical in the matter of API).

I meant documentation in the dpatch file header.  The documentation of
02_public-headers.dpatch says: "Use the public headers directly
internally" ... no mention that types have been fixed, and why.

It really isn't obvious what 02_public-headers.dpatch aims to do and
why, it looks very dangerous (which is why this bug report was
initially written).

By the way, why does the patch change a string to an int8_t*?
(NeAACDecGetErrorMessage)

Max



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to