Difference between revisions of "User talk:Thesbros"
(Clarification - they're not API's, they're access-methods to the native API's.) |
m (fix link) |
||
| Line 16: | Line 16: | ||
How do you define API? Something that can be loaded with <code>os.loadAPI</code>? Well, then [[Monitor (API)|<code>monitor</code>]] is not an API, nor is [[Printer (API)|<code>printer</code>]]. | How do you define API? Something that can be loaded with <code>os.loadAPI</code>? Well, then [[Monitor (API)|<code>monitor</code>]] is not an API, nor is [[Printer (API)|<code>printer</code>]]. | ||
| − | To me, it seems reasonable to say that anything returned by <code>peripheral.wrap</code> is a [[Category:Peripheral APIs|Peripheral API]], and by association, an API. Both [[workbench (API)]] and [[modem (API)]] are returned by peripheral.wrap. | + | To me, it seems reasonable to say that anything returned by <code>peripheral.wrap</code> is a [[:Category:Peripheral APIs|Peripheral API]], and by association, an API. Both [[workbench (API)]] and [[modem (API)]] are returned by peripheral.wrap. |
[[User:Eric|Eric]] 17:11, 20 January 2013 (MSK) | [[User:Eric|Eric]] 17:11, 20 January 2013 (MSK) | ||
* The [[peripheral.wrap]] method provides access to native functions, and does '''not''' return an API - it returns ''access methods'' to the functions of the wrapped blocks and the API's provided by the block, and allows invoking of the block's API(s). For example, wrapping a modem does not create "modem" API - it provides native access to the Rednet API functions. ''[[User:AfterLifeLochie|AfterLifeLochie]] 17:38, 20 January 2013 (MSK)'' | * The [[peripheral.wrap]] method provides access to native functions, and does '''not''' return an API - it returns ''access methods'' to the functions of the wrapped blocks and the API's provided by the block, and allows invoking of the block's API(s). For example, wrapping a modem does not create "modem" API - it provides native access to the Rednet API functions. ''[[User:AfterLifeLochie|AfterLifeLochie]] 17:38, 20 January 2013 (MSK)'' | ||
Latest revision as of 05:14, 26 March 2014
IRC Bot test
Change "ComputerCraft; (+22)" (CID:4756)
Your change on the page "ComputerCraft" (CID:4756) deleted the redirect "ComputerCraft" to "Main Page". This is a critical redirect, as there are more than fifty pages that link to the ComputerCraft page.
In future, please check using the "What Links Here" tool on the left sidebar before marking pages for deletions, or, deleting redirects - and ultimately, check with an Administrator before completely removing the redirect. Tagging a redirect page with the {{delete}} does not prevent redirection (and helps retain integrity), but alerts us to the need (or not) to delete said page. AfterLifeLochie 00:18, 10 December 2012 (MSK)
Crafting Table
ThesBros, is there any chance of adding content to the crafting table page? Or just making it redirect to the MC wiki please? Jonjon1234 01:18, 10 December 2012 (MSK)
X is not an API
How do you define API? Something that can be loaded with os.loadAPI? Well, then monitor is not an API, nor is printer.
To me, it seems reasonable to say that anything returned by peripheral.wrap is a Peripheral API, and by association, an API. Both workbench (API) and modem (API) are returned by peripheral.wrap.
Eric 17:11, 20 January 2013 (MSK)
- The peripheral.wrap method provides access to native functions, and does not return an API - it returns access methods to the functions of the wrapped blocks and the API's provided by the block, and allows invoking of the block's API(s). For example, wrapping a modem does not create "modem" API - it provides native access to the Rednet API functions. AfterLifeLochie 17:38, 20 January 2013 (MSK)
