Hello, you have come here looking for the meaning of the word Module talk:arguments. In DICTIOUS you will not only get to know all the dictionary meanings for the word Module talk:arguments, but we will also tell you about its etymology, its characteristics and you will know how to say Module talk:arguments in singular and plural. Everything you need to know about the word Module talk:arguments you have here. The definition of the word Module talk:arguments will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofModule talk:arguments, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
Along with Module:math. Imported by User:Mxn for the sake of having a two-line rounding function (which does not even depend on most of this code) for his archive navigation module. I doubt we will ever need this in the dictionary proper. Not nominating Module:yesno, but we seem to have managed without it until now, so it might go as well. Keφr14:04, 30 December 2013 (UTC)Reply
I'm inclined to say keep, but remove what we don't really need. I think it would be nice to be able to avoid the constant "if x == "" then x = nil end" on all parameters, it does get tedious. I've thought of writing a module like this before. There's also something else I've wanted to add, which is checking arguments for usage, and a global category tracking system.
Checking arguments for usage would mean that each argument that gets used by the module is marked "used", and at the end if any arguments remain unused, this adds a category or error or something like that. That would allow us to find out easily which pages are using modules with mis-typed parameter names, or parameters that aren't actually recognised or supported by the template.
Tracking categories globally would make it much easier for any module to add tracking categories and such. In templates, you can just put a category anywhere and it works, but in modules you can't do that, which is a limitation. —CodeCat14:21, 30 December 2013 (UTC)Reply
I cannot imagine why we would ever write something that would require Module:math. It mostly wraps basic mathematical functions so that templates can use them: we would probably do most of the work inside modules, making the wrappers unnecessary.
As for Module:arguments… I am unsure what that thing actually does. Looks like some kind of input sanitisation. For now I would prefer to do it directly in the modules which receive a frame. I actually do have one idea for a module for tracking argument usage, categories and errors, but this module would not be of much help there. Keφr18:38, 28 January 2014 (UTC)Reply
I think it might as well be deleted. I am considering making a module that fulfills a similar purpose, but I'd be rewriting it from scratch. —CodeCat18:32, 12 January 2015 (UTC)Reply
Along with Module:math. They were nominated for deletion by Kephir and CodeCat seemed to have some reason to keep them that was unclear to me. A great deal more time has passed and neither she, nor anyone else, has used either of these modules, and for good reason — we don't need them. See Module talk:arguments for the last deletion debate, which was closed as no consensus. —Μετάknowledgediscuss/deeds20:15, 8 April 2017 (UTC)Reply