3 ms·
No, I am not talking about a runtime-allocated structure. I’m talking about a function that can accept and operate on arrays of different sizes, all of which ar
by chongli 3y ago
No, I am not talking about a runtime-allocated structure. I’m talking about a function that can accept and operate on arrays of different sizes, all of which are fixed size at their declaration site, and all stored on the stack.
There is no reason this shouldn’t be possible. It should not require fat pointers at all because the size information is known at compile time.
- School-Cotton 3y agoAFAICT you’d either have to pass the length at runtime somehow, or treat the function as a generic/template and generate a separate version for each separate N it’s called with. The latter would be pretty far from the ethos of C, imo.
- chongli 3y agoThis could be done by storing the length of the array before the first element. It wouldn’t even need to be done in all cases, only if the length is actually used.
- usefulcat 3y ago> AFAICT you’d either have to pass the length at runtime somehow This is exactly the solution proposed in TFA..