Talk:Function Dump
Ok, these aren't in-game functions that you define, people. These are built into the Lua system, they work differently.
Leave the page, it's what it needs to be. It could probably use some better documentation on what each thing does, but DO NOT add any more functions unless I'm missing some from the system, such as delay().
All the functions that Waffle added are nothing more than the connect function. Now, that function needs to be added, but I want to get a list of all of the non-standard functions like "connect()" and "delay()" before I go adding any.
---Mr Doom Bringer 10:57, 3 September 2007 (CDT)
Hey, who edited the Function Dump, spammers. *Sigh.* I don't know how to change to the prev. revision... ---Twila27 6:29, 13 Oct. 2007 (CST)
Hey, what about error()? I think it's an easier way of forcing errors than that other function. It works, too.--tgp1994 15:19, 8 September 2008 (CDT)
>This page is getting a little long, perhaps we should put the examples as subpages? -Mindraker
I think we ought to just leave it the way it was, for now. You pretty much have to know something about Lua to understand any of these, so you'll know enough to be able to try the function yourself if you need an example.Nevermind, now it's looking really good =P. Since it's so large, we should divide it by libraries: /Basic Functions, /Coroutine Manipulation, /String Manipulation, etc... --Anaminus 17:18, 7 October 2008 (CDT)
- Oh, ok, like Function Dump/Basic Functions? Yeah it's getting a little big. MINDRAKER 19:49, 13 October 2008 (CDT)
- I'm liking this formatting, but could we get small examples using the function, not just the output?
- As for sub pages, go for it. In fact... ---Mr Doom Bringer 20:57, 13 October 2008 (CDT)
I think that we should have seperate pages for each of the functions as to allow more information. They could be like the method pages but would say something like "This is a core function" rather than "In object(s)". We'll have to do something eventually if Roblox keeps adding new functions. EDIT Made an early template.--ArceusInator (talk | contribs) 04:01, 23 March 2011 (UTC)
- The current pages don't seem big enough that they need to be further divided. What extra information could be added that would make them too large? --Anaminus 04:31, 23 March 2011 (UTC)
- Say we find something cool that you can do with pcall, but it takes a while to explain it. That's when you would want a seperate page. We would keep all of the sections we have but each section would have a smaller explanation and link to the larger one, which would link back to the smaller one in the "type" part of the template. Also, say Roblox runs for 30 more years. They're probably gonna release a LOT of new functions and we _will_ eventually have to do something like this.--ArceusInator (talk | contribs) 12:56, 23 March 2011 (UTC)
- Sure, if a section gets too large, then it makes sense to move it to a new page. However, it doesn't make sense to move them all in anticipation that they're going to be expanded upon later. You really don't know what's going to happen, so just do it when it's necessary.
- Also, I don't think it needs yet another template. --Anaminus 18:11, 23 March 2011 (UTC)
- Say we find something cool that you can do with pcall, but it takes a while to explain it. That's when you would want a seperate page. We would keep all of the sections we have but each section would have a smaller explanation and link to the larger one, which would link back to the smaller one in the "type" part of the template. Also, say Roblox runs for 30 more years. They're probably gonna release a LOT of new functions and we _will_ eventually have to do something like this.--ArceusInator (talk | contribs) 12:56, 23 March 2011 (UTC)
