Pull overloaded functions out into separate .m files
suever opened this issue · comments
This would help with checking for errors. Initially they were all placed within the .octaverc file but we can put them in separate files and just source each of them from within the .octaverc. This should work, but we'll have to do some testing to make sure.
This is actually done already by placing them within @funcname/funcname.m so that the class is resolved before the function even in cases where the functions are built-ins. This way they can live as .m files AND not have to be combined into an .octaverc in some hacky way.