L4Re - L4 Runtime Environment
L4Re::Ned::Cmd_control Class Reference

Direct control interface for Ned. More...

Inherits L4::Kobject_0t< Derived, PROTO, S_DEMAND >.

+ Collaboration diagram for L4Re::Ned::Cmd_control:

Public Member Functions

long execute (L4::Ipc::String<> cmd) noexcept
 Execute the given Lua code. More...
 
long execute (L4::Ipc::String<> cmd, L4::Ipc::String< char > *result) noexcept
 Execute the given Lua code. More...
 

Detailed Description

Direct control interface for Ned.

Definition at line 20 of file cmd_control.

Member Function Documentation

◆ execute() [1/2]

long L4Re::Ned::Cmd_control::execute ( L4::Ipc::String<>  cmd)
inlinenoexcept

Execute the given Lua code.

Parameters
[in]cmdString with Lua code to execute.
Return values
L4_EOKCode was successfully executed.
-L4_EINVALCode could not be parsed.
-L4_EIOError during code execution.

The code is executed using the global Lua state of ned which is retained between successive calls to execute. Thus you may define data in one call to execute and use it in a subsequent call.

This function does not return any results from the execution of the Lua code itself.

Definition at line 43 of file cmd_control.

◆ execute() [2/2]

long L4Re::Ned::Cmd_control::execute ( L4::Ipc::String<>  cmd,
L4::Ipc::String< char > *  result 
)
inlinenoexcept

Execute the given Lua code.

Parameters
[in]cmdString with Lua code to execute.
[out]resultThe first return value of the Lua code block as string.
Return values
L4_EOKCode was successfully executed.
-L4_EINVALCode could not be parsed.
-L4_EIOError during code execution.

The code is executed using the global Lua state of ned which is retained between successive calls to execute. Thus you may define data in one call to execute and use it in a subsequent call.

Definition at line 65 of file cmd_control.

References L4::Kobject_t< Derived, L4::Kobject, PROTO, S_DEMAND >::c().

+ Here is the call graph for this function:

The documentation for this class was generated from the following file: