The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Source string Source string

221/10000 · 221
English Actions
There should be one -- and preferably only one -- obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
https://www.python.org/dev/peps/pep-0020/
Indentation and formatting
4 spaces instead of tabs. PIL suggests using two spaces, but a programmer looks at code from 4 to 8 hours a day, so it's simpler to distinguish indentation with 4 spaces. Why spaces? Similar representation everywhere.
You can use vim modelines:
-- vim:ts=4 ss=4 sw=4 expandtab
A file should ends w/ one newline symbol, but shouldn't ends w/ blank line (two newline symbols).
Every do/while/for/if/function should indent 4 spaces.
Related ``or``/``and`` in ``if`` must be enclosed in the round brackets (). Example:
-- Good
if (a == true and b == false) or (a == false and b == true) then
<...>
end

-- Bad
if a == true and b == false or a == false and b == true then
<...>
end

-- Good but not explicit
if a ^ b == true then
end
Type conversion
Do not use concatenation to convert to string or addition to convert to number (use ``tostring``/``tonumber`` instead):
-- Bad
local a = 123
a = a .. ''

-- Good
local a = 123
a = tostring(a)

-- Bad
local a = '123'
a = a + 5 -- 128

-- Good
local a = '123'
a = tonumber(a) + 5 -- 128
Try to avoid multiple nested ``if``'s with common body:
-- Good
if (a == true and b == false) or (a == false and b == true) then
do_something()
end

-- Bad
if a == true then
if b == false then
do_something()
end
if b == true then
if a == false then
do_something()
end
end
Avoid multiple concatenations in one statement, use ``string.format`` instead:
-- Bad
function say_greeting(period, name)
local a = "good " .. period .. ", " .. name
end

-- Good
function say_greeting(period, name)
local a = string.format("good %s, %s", period, name)
end

-- Best
local say_greeting_fmt = "good %s, %s"
function say_greeting(period, name)
local a = say_greeting_fmt:format(period, name)
end
Use ``and``/``or`` for default variable values
-- Good
function(input)
input = input or 'default_value'
end

-- Ok but excessive
function(input)
if input == nil then
input = 'default_value'
end
end
``if``'s and return statements:
-- Good
if a == true then
return do_something()
end
do_other_thing()

-- Bad
if a == true then
return do_something()
else
do_other_thing()
end
Using spaces:
Don't use spaces between function name and opening round bracket. Split arguments with one whitespace character:
-- Bad
function name (arg1,arg2,...)
end

-- Good
function name(arg1, arg2, ...)
end
Add a space after comment markers:

Loading…

User avatar None

New source string

testing_project / Documentation: dev_guide/lua_style_guide — English

-- Good
if (a == true and b == false) or (a == false and b == true) then
<...>
end

-- Bad
if a == true and b == false or a == false and b == true then
<...>
end

-- Good but not explicit
if a ^ b == true then
end
a year ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
string 38