You may have been lead here because of my post on Roblox, or you may just be checking this site. I don't care. Here is what's wrong:


THE FUNCTION:

Code:

local function runScript(msg)
if string.sub(msg, 1, 4):lower() == string.lower("run/") then
print(msg:sub(5) .. " return 1")
local str = loadstring(string.sub(msg, 5) .. " return 1")
getfenv(str).print = OutputPrint -- a function I made
local stat, err = coroutine.resume(coroutine.create(str))
print(stat, err)
repeat wait() until not stat or err == 1 -- I'm still experimenting with this part, but I can't test it until I get the loadstring stuff fixed
print(stat, err)
if err == 1 then
script.Parent.Text = "It worked :D"
wait(3)
script.Parent.Text = "Output GUI"
else
script.Parent.Text = tostring(err)
end
end
end

runScript([[run/print("Hello") wait(1) error("wut")]])

THE OUTPUT:

Fri Mar 11 23:43:13 2011 - [string "print("Hello") wait(1) error("wut") return ..."]:1: wut
Fri Mar 11 23:43:13 2011 - [string "print("Hello") wait(1) error("wut") return 1"], line 1 stack end

I've been trying to fix my SB, 'cause ever since I switched it from pcall to coroutines, it just didn't work. Obviously, the error is coming from the loadstring stuff, but I don't understand why, since coroutine.resume is supposed to run stuff in protected mode ._.

HALP.

I've modified part of it and it might work:

local function runScript(msg)
if string.sub(msg, 1, 4):lower() == string.lower("run/") then
print(msg:sub(5))
local stat, err = loadstring(string.sub(msg, 5))
print(stat, err)
if not err then
script.Parent.Text = "It worked :D"
wait(3)
script.Parent.Text = "Output GUI"
else
script.Parent.Text = err
end
end
end

runScript([[run/print("Hello") wait(1) error("wut")]])

and the error message that was in the output before was because you used the function 'error' to print 'wut' as an error message.

@Bluey: I'm using coroutines because they should run in protected mode (kinda like pcall). I highly doubt that your "solution" would work :o

But without this, my SB will never be fixed D:

You couldn't just take all the code out of the function, adjust it to still work, and then run it to find out what line(s) was wrong? I would, but I don't have enough time right now.

I think your's works actually! noticed how you used the error() function instead of print()?

Error is fun?

I'm just changing 1 function:

local function runScript(msg)
if string.sub(msg, 1, 4):lower() == string.lower("run/") then
print(msg:sub(5) .. " return 1")
local str = loadstring(string.sub(msg, 5) .. " return 1")
getfenv(str).print = OutputPrint -- a function I made
local stat, err = coroutine.resume(coroutine.create(str))
print(stat, err)
repeat wait() until not stat or err == 1 -- I'm still experimenting with this part, but I can't test it until I get the loadstring stuff fixed
print(stat, err)
if err == 1 then
script.Parent.Text = "It worked :D"
wait(3)
script.Parent.Text = "Output GUI"
else
script.Parent.Text = tostring(err)
end
end
end

runScript([[run/print("Hello") wait(1) print("wut")]])

But error is fun D:

'[string "print("Hello") wait(1) error("wut") return ..."]:1: wut'
that is the output that is meant to to happen because of this: 'error("wut")'

hmmm. sigh* do strings in lua have to be that complicated?

Yes, they do. For some reason, they do.

*rage* THE PROBLEM HAS NOTHING TO DO WITH STRINGS. if you look up the function error() on wiki it'll tell you that it makes error messages in the output.