Displaying 3 results from an estimated 3 matches for "flac__xxxx".
2015 Oct 07
2
Are pointers to FLAC__int32 and int interchangeable?
There are following functions in bitreader.c:
FLAC__bool FLAC__bitreader_read_unary_unsigned(FLAC__BitReader *br, unsigned *val);
FLAC__bool FLAC__bitreader_read_rice_signed(FLAC__BitReader *br, int *val, unsigned parameter);
FLAC__bool FLAC__bitreader_read_rice_signed_block(FLAC__BitReader *br, int vals[], unsigned nvals, unsigned parameter);
* function FLAC__bitreader_read_rice_signed():
2015 Oct 07
0
Are pointers to FLAC__int32 and int interchangeable?
...g
ptr ++ ;
The next address that the pointer points to is calculated using:
ptr = (sometype_t *) ((char*) ptr) + 1) ;
where incrementing a char* pointer increases the address by 1.
> (the same question for FLAC__uint32* and unsigned*)
Very similar.
Personally I think the FLAC__xxxx stuff should go, to be replaced with
C standard int32_t, uint32_t, int16_t etc, at least for internal code.
I am slowly doing that when I touch code.
I don't think this should be done at the API level without an API
version bump and I don't think that is currently worth it.
HTH,
Erik
--...
2015 Oct 08
1
Are pointers to FLAC__int32 and int interchangeable?
Erik de Castro Lopo wrote:
> Well FLAC__int32 is just a 32 bit integer and on all the platforms/
> architecures/compilers that FLAC supports FLAC__int32 and int are
> the same.
>
> Personally I think the FLAC__xxxx stuff should go, to be replaced with
> C standard int32_t, uint32_t, int16_t etc, at least for internal code.
> I am slowly doing that when I touch code.
>
> I don't think this should be done at the API level without an API
> version bump and I don't think that is currently w...