Jump to content

[SOLVED] improvement on the uniginescript error log


photo

Recommended Posts

Posted

hi:

   Since there is no good debugger for the script. so the log is very important to discover bugs.

sometimes the log doesn't say which line. i have to check for a longer time to find it.

example: when you have a wrong “{”“}” brace pair or sometime like the following

"16:13:12 Variable::operator!=(): bad operands string and int"

  which is that i use a string in a wrong place, but it doesn't say which line.

 

 

Posted

Hi,

It's already in the feature list, but we can't give any ETA, as it's not the top of the list. Sorry.

  • 3 weeks later...
Posted

it's should be easier to debug

21:27:13 ---- Game Framework Plugin ----
21:27:13 Version: 0.01
21:27:13
21:27:13 Parser::check_braces(): some errors with count of '{' and '}' symbols
21:27:13 Parser::preprocessor(): wrong number of braces
21:27:13 Parser::preprocessor(): can't load "memory" file
21:27:13 Interpreter::addExpression(): can't parse expression
21:27:13 Game::LogicModules::compile(): Can't compile logic module
21:27:13 FrameworkEditor::load_logic(): Can't compile a game logic.
21:27:13 FrameworkEditor::load_data(): Can't build the entity tree.
21:27:13 Editor::editor_load(): editor is already loaded
  • 4 weeks later...
×
×
  • Create New...