Engine:CCMD lua.lua edit: Difference between revisions

From AddOn Studio
Jump to navigation Jump to search
Tag: Reverted
 
(3 intermediate revisions by the same user not shown)
Line 37: Line 37:
run `print(1+2);print(1+2)`;exit
run `print(1+2);print(1+2)`;exit
</kua>
</kua>
Thus, when run directly in the context the first one works and the second one doesn't, third does:
And this fails because 'if', 'print', and 'end' are in separate script statements:
<kua>
<kua>
contexct lua
context lua
function bob(s) print(s) end
if bob then -- Lua errer!
bob("fred")
   print(1 + 2)
> fred
</kua>
<kua>
function bob(s)  -- Lua syntax error!!!
   print(s)
end
end
bob("james")
</kua>
</kua>
These work:
<kua>
<kua>
run `function bob(s)  -- Lua syntax error!!!
context lua
   print(s)
run `if bob then
   print(1 + 3)
end`
end`
bob("alan")
if bob then print(1 + 4) end
> alan
</kua>
</kua>



Latest revision as of 21:57, 18 October 2023

Console commands

Runs a Lua statement in a Lua runtime.

lua print("fred")

Arguments[edit]

  • name - (none)
  • value - the verbatim Lua code to be run

Associations[edit]

  • Is by default placed in the 'lua' context.
  • Is the default command for the 'lua' context.
  • Does not have its own command name in 'lua'.

Details[edit]

Used to run a Lua text directly in the 'lua' context, if the first statement is not engine command, variable or alias in the 'lua' context. This allows the script in the 'lua' context to act as though it were running directly in a Lua console.

While the 'lua' context has the ability to hold variables and aliases, they cannot be created from script as the 'lua' context has no 'alias', 'set' or 'var' type script commands added to the context.

Line by line processing

The 'lua_edit' default command will only be run when a statement is not another context, or a command, variable, or alias. Script in the 'lua' context is still run statement by statement, as script in the engine.

For example:

context lua
print(1+2); exit

Is actually:

context lua
print(1+2) -- sent to Lua runtime
;          // script statement delimiter processed in script
exit       // script

This however would run ';' delimited statements in one Lua chunk, using the 'lua' context 'run' command. And then still run the script 'exit' command:

context lua
run `print(1+2);print(1+2)`;exit

And this fails because 'if', 'print', and 'end' are in separate script statements:

context lua
if bob then -- Lua errer!
   print(1 + 2)
end

These work:

context lua
run `if bob then
   print(1 + 3)
end`
if bob then print(1 + 4) end
Outer return statement

If the outer scope of the Lua code calls return, the return values will be printed. For example:

context lua
a = 1
return a
return 100 + 1000

Will write '1' and '1100' to the engine log/console.

This is similar to an interactive Lua console's '=' convenience command like =100, where will output '100' in the console when '=' starts a console line, after the command is run. In the engine real Lua interactive console, and this mechanism is special to only 'lua_edit', and is provided for similar convenience.

Examples[edit]

Default values[edit]

Below, 'exit' is actually a 'lua' context command, which simply switches to the 'global' context. It is not run in a Lua runtime.

context lua
print(1 + 2)
exit
Prints '3'.

Dual inline scripting[edit]

Run Lua from script:

lua print(1 + 2)
> 3

Run script from lua:

var bob fred
context lua
script 'bob'
> fred
exit

Together fluidly:

lua print(1 + 2)
> 3
bob
> fred
context lua
print(1 + 2)
> 3
script 'bob'
> fred

Inline scripting[edit]

Lua and JS from script:

var bob fred
lua print(1 + 2)
js print(1 + 3)
bob
context lua
print(1 + 4)
script 'bob james;bob'
exit
context js
print(1 + 5);
script('bob alan;bob');
exit
> 3
> 4
> fred
> 5
> james
> 6
> alan

With blocks:

var bob fred
bob
lua run `
   local s = script
   print(1 + 4)
   s 'bob james;bob'
   s 'js function alan(s) { script("bob "+s+";bob"); }'
`
js alan("alan");
> fred
> 5
> james
> alan

Notes[edit]

  • While 'lua_edit' is intended make console Lua commands easy to run, can allow scripts and other types of macros to avoid lots of situations where complex logic would otherwise be required, by simply switching to the 'lua' context and then running a series of single line lua chunks.