I also think it makes sense to specify arguments to tabread~ (or delread~) to specify the interpolation.
Dan you are suggesting an api like this to manage code size and structuring. I see, because when we put everything into the tabread~ (or delread~) class with just flags from arguments/messages, it would get hard to maintain.
E.g. for tabread: So we would create a header „d_array.h" with the function declarations? Should every interpolation type have its own function declaration or do we override for different types? (A bit like an abstract class, but I don’t know how this works in C) The definitions would still go into „d_array.c“?
Refactoring and testing this could take quite some time...
Am 2021-05-04 um 04:35 schrieb Alexandre Torres Porres porres@gmail.com:
Em seg., 3 de mai. de 2021 às 12:52, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> escreveu: Maybe I'm opening a can of worms, but I could imagine tabread etc taking an argument to specify which algorithm to use among a (small) list of those available. The current algorithm would be the default so as not to break existing patches. :)
I had suggested the same! ;) _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list