Can We Have Line Numbers For LUA Errors?

[Davaris]

I was going through the LUA Tute and saw it has a debugger, which tells you when you have an error which is great. The only problem is it doesn't tell you what line number the error is on.

 

So my request is can we have line numbers included in the error report?

 

 

Once a script starts to become large and complicated, no line numbers on the error messages, will make them very difficult to find.

 

 

 

 

--Register abstract path 

RegisterAbstractPath("") 

--Set graphics mode 
if Graphics(1024,768)==0 then 
Notify("Failed to set graphics mode.",1) 
return
end 

world=CreateWorld() 

if world==nil then 
Notify("Failed to initialize engine.",1) 
return 
end 

mesh=CreateMesh() 

mesh:Point(nil)

[Josh]

I am looking into this...

[TylerH]

Yay for no one looking at my debug.Trace library I posted a month or so ago?

[Josh]

It's all in the presentation.

[Rick]

It's all in the presentation.

 

 

This couldn't be more true. It matters little if you have the best widget in the world, if it's not presented well, it just won't get used. The life of Linux.

[AggrorJorn]

is there any progress on this?

[Josh]

This will be included in version 2.32. The main editor even gives debug info on crashes that occur during a Lua script execution.