Updated alias and samenv docs (M.Z.)
This commit is contained in:
@ -20,22 +20,28 @@ access internal SICS interfaces like the drive command or
|
||||
others. Object aliases are installed into SICS with the SICSAlias
|
||||
command:
|
||||
<DL>
|
||||
<DT>SicsAlias newname oldname
|
||||
<DT>SicsAlias oldname newname
|
||||
<DD>This command installs newname as alias for the object oldname.
|
||||
</dl>
|
||||
SicsAlias can only be used within initialization scripts. SicsAlias is
|
||||
considrered deprecated and can be replaced with the superior runtime
|
||||
considered deprecated and can be replaced with the superior runtime
|
||||
aliases described below.
|
||||
</p>
|
||||
<h2>Runtime Aliases</h2>
|
||||
<p>
|
||||
Runtime aliases are full object aliases which can be configured into the
|
||||
system at run time by a SICS manager. The syntax looks like this:
|
||||
system at run time by a SICS manager.
|
||||
The syntax looks like this:
|
||||
<dl>
|
||||
<dt>definealias SICSobject aliasname
|
||||
<dt>DefineAlias aliasname SICSobject
|
||||
<dd>This defines aliasname to be the alias for the SICS object SICSobject.
|
||||
<dt>definealias aliasname
|
||||
<dd>This command deltes the alias aliasname.
|
||||
It is not needed that SICSobject already exists. If SICSobject is already
|
||||
an alias, it is translated before definition.
|
||||
Multiple translation is possible, depending on the order of definition.
|
||||
When an alias is used, and it does not point to an existing object,
|
||||
the behaviour is the same as if an unknown object would have been used.
|
||||
<dt>DefineAlias aliasname
|
||||
<dd>This command deletes the alias aliasname.
|
||||
</dl>
|
||||
</p>
|
||||
<h2>Command Aliases</h2>
|
||||
|
Reference in New Issue
Block a user