Perl6-Math-Matrix
Perl6-Math-Matrix copied to clipboard
pierre-vigier
class breakup
as the class gets bigger and bigger I plan to split the code into partial classes, but leave the namespace for most part. I think operators with get their own file first.
How would you do that? role composition for specific function? like Matrix::Triangular to overwrite some behaviour? not sure to get how the split would work, but indeed, the class is getting a bit too big
i spoke just about breaking it up into files. not functional subclasses. good candidates are decompositions and ops but each bring reduction of only ~100 lines, but I will do it anyway because there separate sections and also good for documentations (linkable sections). On other hand most of code is not complicated so there is not much to encapsulate. this is also one reason to put decomposition into subclass because they are more complicated so you get the abstraction effect by hiding it into another file.
Not decided - But open issue for me now.
a huge step will be outsource pod into own file. this has also additional advantage that to generate the readme, we don't have to cat together several converted files. disadvantage though: pod no longer attached to methods and cant use the why metamethod but didnt figured that how to use it anyhow.
I looked into it and its much harder to do than expected, think i should factor out other things first like special array and special array of array generation