https://bugs.documentfoundation.org/show_bug.cgi?id=89387
--- Comment #48 from Sarrah <[email protected]> --- (In reply to Buovjaga from comment #47) > (In reply to Sarrah from comment #46) > > (In reply to Buovjaga from comment #45) > > > (In reply to Sarrah from comment #44) > > > > Since the last patch (Comment 42), are the rest of the functions > > > > (ScInterpreter::CalculatePearsonCovar, > > > > ScInterpreter::CalculateSlopeIntercept, etc) still available to be > > > > worked > > > > on? If yes, I would like to work on them. > > > > > > You mean if anyone else is working on them? I'm not seeing any open patch > > > at > > > least: https://gerrit.libreoffice.org/q/message:89387+status:open > > > > Yeah, both if anybody is working on it and which, if any of the functions > > still need to be worked on, with a similar template as given in the > > description. > > Kinda doing your homework for you, but based on comment 37 and the commit in > comment 42, these are still left: > ScInterpreter::CalculatePearsonCovar > ScInterpreter::CalculateSlopeIntercept > lcl_MatrixCalculation in interpr5.cxx > ScInterpreter::CheckMatrix Right, thanks! Had a vague idea based on the comments as I mentioned in comment 44 too, however I couldn't find the CalculatePearsonCovar() and CalculateSlopeIntercept() functions, (atleast in the same file as the others) hence asked. On studying all commits that tag this issue, I have found the last patch made for GCD and LCM functions, and then a few on another issue to resolve a bug in strings caused by this patch. I'll be trying to work on the ScInterpreter::CheckMatrix, as I see it still uses a for loop to iterate, and try to keep patch 34110 as a reference. However, on the off-chance that there is something different about this function I should know to avoid the same bugs, do let me know. -- You are receiving this mail because: You are the assignee for the bug.
