Talk:Lua
| This is the talk page for discussing improvements to the Lua article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Archives (index): 1, 2Auto-archiving period: 12 months |
| This It is of interest to multiple WikiProjects. | |||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||
| On 4 April 2025, it was proposed that this article be moved from Lua (programming language) to Lua. The result of the discussion was moved. |
Can embedding Lisp-like code?
e.g.:
quote(string) -> "string" quote(quote(expr)) -> "quote(expr)" quote(quasiquote(expr)) -> "quasiquote(expr)" quote(quasiquote(unquote(expr))) -> "quasiquote(unquote(expr))" quote(unquote(expr)) -> "unquote(expr)" quasiquote(string) -> "string" quasiquote(quote(expr)) -> "quote(expr)" quasiquote(quasiquote(expr)) -> "quasiquote(expr)" quasiquote(unquote(expr)) -> expr
Created for political reasons?
Seems to imply Lua was created for political reasosn but no proof is provided.
"From 1977 until 1992, Brazil had a policy of strong trade barriers (called a market reserve) for computer hardware and software, believing that Brazil could and should produce its own hardware and software. In that climate, Tecgraf's clients could not afford, either politically or financially, to buy customized software from abroad; under the market reserve, clients would have to go through a complex bureaucratic process to prove their needs couldn't be met by Brazilian companies. Those reasons led Tecgraf to implement the basic tools it needed from scratch.[5]" — Preceding unsigned comment added by ~2026-12627-08 (talk) 21:42, 25 February 2026 (UTC)
Truth is the restrictions on imports finished one year prior.
Problems with "Inheritance" section
The "Inheritance" subcategory in the article is written and phrased in a way that could easily lead a reader to believe believe features such as multiple inheritance are features built into the Lua language. However, the technique is a pattern implemented using metatables, not a language feature.
While the "Object-oriented programming" category above does indeed explain that Lua doesn't have a built-in concept of classes, the addition of the class inheritance section below it seems to deviate from that tone, and it describes a niche pattern that is rarely used; it feels like somebody wrote their own little pet program in Lua and added it to the article masquerading as a feature. 24.68.84.200 (talk) 07:17, 29 September 2024 (UTC)
- The issue has been fixed in this edit: https://en.wikipedia.org/w/index.php?title=Lua&diff=prev&oldid=1323039620 ~2025-34505-43 (talk) 14:00, 19 November 2025 (UTC)
Requested move 4 April 2025
- The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.
The result of the move request was: moved. (closed by non-admin page mover) Cremastra talk 20:20, 11 April 2025 (UTC)
– Lua (programming language) is clearly the WP:PRIMARYTOPIC. 2600:1700:6180:6290:E1BC:304B:79DF:C9EB (talk) 19:43, 4 April 2025 (UTC)
- Rename yep. * Pppery * it has begun... 19:38, 5 April 2025 (UTC)
- Support I agree, Lua (programming language) is certainly the primary topic here.
- RedactedHumanoid (talk) 19:51, 7 April 2025 (UTC)
- Strong Support the name Lua is more familiar with the programming language than others.saluere, Ɔþʱʏɾɪʊs⚔ 09:59, 11 April 2025 (UTC)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.


