Rémi Denis-Courmont (12023-05-02):
> So it must be very poorly written because C union are supposed to avoid this
> cleanly.
> If you need padding where any sane implementation does not, then it is
> clearly
> poorly written.
I must say, I am impressed by the rudeness and arrogance of such a
Le tiistaina 2. toukokuuta 2023, 19.42.39 EEST Nicolas George a écrit :
> Rémi Denis-Courmont (12023-05-02):
> > A JSON writer that requires forced alignment is a poorly-written JSON
> > parser.
> This JSON writer requires that the structures that contain its state are
> aligned, just like any
Rémi Denis-Courmont (12023-05-02):
> A JSON writer that requires forced alignment is a poorly-written JSON parser.
This JSON writer requires that the structures that contain its state are
aligned, just like any other piece of C code. There is nothing
poorly-written here.
> This is reinventing
Le perjantaina 28. huhtikuuta 2023, 12.55.01 EEST Nicolas George a écrit :
> Signed-off-by: Nicolas George
> ---
> libavutil/extendable.h | 59 ++
> 1 file changed, 59 insertions(+)
> create mode 100644 libavutil/extendable.h
>
>
> FFReservedPadding is
On 4/29/2023 9:17 AM, Anton Khirnov wrote:
> What important problem within the scope of the project is being solved
> by this? Why do we need over a 1000 lines of just new header files for
> it? Why do we need a generic JSON writer? We are not a JSON library.
> Neither are we a string processing
I've said this before, repeating it again for ease of reference: I do
not believe the use case for this has been sufficiently established.
What important problem within the scope of the project is being solved
by this? Why do we need over a 1000 lines of just new header files for
it? Why do we
Signed-off-by: Nicolas George
---
libavutil/extendable.h | 59 ++
1 file changed, 59 insertions(+)
create mode 100644 libavutil/extendable.h
FFReservedPadding is used by the WIP JSON writer.
diff --git a/libavutil/extendable.h b/libavutil/extendable.h
