Fixed @Lua does not behave as documented

[djspits]

C:\Test :-) >echo %@lua[print "foo"]
foo
print "foo"

Regards, DJ.

 

[mikea]

Seen here as well. But wait! There's more!

c:\takecommand20> echo %@perl[print "foo"]
Error (SYS): Invalid class string
-1

 

[JohnQSmith]

@mikea Check to make sure you have PerlScript installed as per the documentation. I don't have it installed and got the same error.

 

[mikea]

Ah, so this relies on PerlScript, eh? I have never installed it. I'd always thought this kind of problem with Perl pertained to some weirdness with ActiveState's Perl (which is the only version I've used).

 

[rconn]

Fixed in 20.0.22.

 

[JohnQSmith]

Now I get this

[C:\BIN\JPSoft\TCMD20] 11:04:16 $ echo %@lua[print 'foo']
foo
ECHO is OFF

[C:\BIN\JPSoft\TCMD20] 11:04:27 $ %@lua[print 'foo']
foo

 

[rconn]

Echoing the result of @LUA is kind of pointless, as it will always return 0 unless there's an internal Lua error, in which case you'll get an error message and the ECHO will never be executed.

 

[JohnQSmith]

Echoing the result of @LUA is kind of pointless,

I didn't write the example in the user's guide...

 

[vefatica]

Echoing the result of @LUA is kind of pointless, as it will always return 0 unless there's an internal Lua error, in which case you'll get an error message and the ECHO will never be executed.

That doesn't agree with what JQS observed. Why wasn't "0" echoed in his first example? And I would have expected

TCC: Unknown command "0"

from his second example.