Additional ref argumented functions?

[Meetem]

All of the functions now use double pointers for the fields, like avformat_open_input's AVFormatContext**, this is error prone as requires to manually create field on the stack and then update the field in the class (like in the example).
More robust version could be using ref AVFormatContext* or out AVFormatContext* for such a fields.

I know this might be complicated to check on C side, wether it's a double pointer or output write, but making even a draft version can help a lot.

[Ruslan-B]

@Meetem I'll take a look most of them requiring fix arrays most-probably can be wrapped.

[Meetem]

I would've just used unsafe ref -> pointer, but in a real dotnet (not Mono) it's quite hazardous thing to do, as GC might lose the reference, so leaving a ref modifier in extern's arguments will do the job. For the array outputs, I think it's fine to have double pointers. Most of the APIs will only output a single element anyway.

[Ruslan-B]

yes boils down to pointer to an array of type, as we have fixed arrays of arbitrary fixed size can be wrapped in similar manner.
It is indeed most finnicky and confusing point - modern AI is easy will mess your code as well.