RESOLVED: Unexpected textport error messages on regular coms

[ab30]

When i type into the texport, for testing purposes, somme regular commands, it often echoes an unexpected error message.

By example a chop command of the form:

Code: Select all

chop("path:channel")

which does work in an operator parameter, echoes the following error message into the textport:

Code: Select all

Textport (line 0 - ): Command 'chop' not specific enough. Shorthand commands are also deprecated.

Is it a bug ?

[malcolm]

This is probably the more confusing part of tscript. Things like 'chop' are expressions, which are different from commands. You can type commands into the textport and they will just work. For expressions you need to place them in backticks and echo the result.

echo `chop("path:channel")`

This is also true if you put chop() inside a parameter that expects a string. The backticks are how to tell the interpreter that you are giving something that should be evaluated, not just a string.

The main difference between an expression and a command is that a command does something, while an expression only ever returns a result, they never change the state of the system (except for possibly cooking nodes to get their results).

[ab30]

Yet i knew about the difference between expressions and commands, but surely the "Command 'chop' not specific enough" message got me more confused, strenghtening the erroneous thought that it was a command...

Thanks for having clarified this up