https://bugs.documentfoundation.org/show_bug.cgi?id=172799
--- Comment #17 from Ben Urban <[email protected]> --- (In reply to ady from comment #16) > Just with that, it shows the lack of both knowledge and experience with > spreadsheet tools, particularly with functions and errors in formulas. I do > not want to waste my time. I would strongly recommend against attempting to insult people that you know little about (or even people you know a lot about, for that matter). Many people don't appreciate it. In particular, I happen to agree with Eyal, and a claim that I am not intimately familiar with spreadsheets makes you sound deluded. But feel free to stop wasting our time here. We will be happy to discuss this without you. > There are more than enough problems that have no alternative nor workaround > for users. Anyone that would have the required knowledge, experience and > resources to adequately improve the hints for error codes in Calc should > rather improve the really much-more-serious limitations and problems that > let users with no alternative at all. There are too many of those (that have > been awaiting for solutions for years), and a lack of devs with the required > knowledge and experience to adequately solve the serious problems Calc has > in its Functions. Then, by all means, tell me what I should work on instead. I would appreciate knowing where to direct my efforts, to maximize my value to the project. For what it's worth, one reason I chose to add LAMBDA as my first contribution is because it can be used to implement most of the functions in a spreadsheet. Now, a user can work around missing or faulty functions, if they have a thorough knowledge of computer science (as you seem to expect every user to have). With just LAMBDA and MAKEARRAY, for instance, one can write BYCOL, BYROW, MAP, and RANDARRAY, along with many others. REDUCE adds another class of functions on top of that. For what it's worth, As much as I believe the bare error number should not be shown at all, the short message associated with that code is still inadequate in most cases. Hence my desire to somehow provide more specific information about each error. At this point, I'm trying to figure out what would be the best way to provide the relevant information. I also would appreciate it if someone can suggest where to look in the code to implement the UI stuff (I've been working on formula internals and have barely touched the UI). -- You are receiving this mail because: You are the assignee for the bug.
