 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Thu Oct 04, 2007 2:40 am
[2.04 Lua] Weird error |
I have no idea what could cause these messages, but I was getting messages printed to the screen in cyan like
ERROR: unary operator requires two arguments
ERROR: function unmatched paranthesis something something
That's not how normal Lua errors are displayed, so I was very confused. I was running simple code like
functon lol (msg) error(msg) end
or
for k in pairs(_G) do print(k) end
And these errors were appearing. |
|
|
 |
Arde Enchanter
Joined: 09 Sep 2007 Posts: 605
|
Posted: Thu Oct 04, 2007 4:19 am |
Very similar (in style) to my case http://forums.zuggsoft.com/forums/viewtopic.php?t=28400 - double ERROR messages and wrong number of arguments mention, appeared first in 2.04. Think this is related to these threading issues Zugg trying to fix now. Will wait till 2.05 before report any further.
|
|
_________________ My personal bug|wish list:
-Wrong Priority when copy-paste setting
-1 prompt trigger for Mapper, Session and General Options, not 3 different!
-#SECTION can terminate threads
-Buttons can't start threads |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Oct 04, 2007 5:17 pm |
When you get an error message displayed in the MUD window like that, it means that an alias (or other script) that was executing in the background had an error in the CMUD execution module. Since this can happen many threads deep into a complex script, CMUD doesn't abort and raise a normal exception, but instead just displays the error to the screen. So, these errors should normally only occur when using zScript stuff. Make sure your script was marked as "Lua" and not "zScript".
This is actually totally different than the error reported by Arde, since they don't have anything to do with Lua. |
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Thu Oct 04, 2007 6:17 pm |
It wasn't an alias, it was on the command line, and I was very much in Lua mode (or it seemed that way, at least) when it happened.
|
|
|
 |
Arde Enchanter
Joined: 09 Sep 2007 Posts: 605
|
Posted: Thu Oct 04, 2007 6:21 pm |
An error is different, but I told about how the error report look like. Since its not a Lua error msg, it is the message from CMUD itself. And these messages from CMUD I see in CMUD since 2.04.
If you say "it is different" - ok, it is different. Let's wait till 2.05 and see.  |
|
_________________ My personal bug|wish list:
-Wrong Priority when copy-paste setting
-1 prompt trigger for Mapper, Session and General Options, not 3 different!
-#SECTION can terminate threads
-Buttons can't start threads |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Oct 04, 2007 7:14 pm |
Hmm, you definitely shouldn't be getting those kind of errors when using the Lua command line. But, I just typed:
Code: |
for k in pairs(_G) do print(k) end |
into the Lua command line and got the same result, so at least I can reproduce it. Thanks for the report. |
|
|
 |
|
|