123
-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|616|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> Monkey Says No!

Mon, 18 Mar 2013, 17:22
spinal
dammit, monkeys cryptic error messages are worse than xcodes debugger.

-=-=-
Check out my excellent homepage!
Mon, 18 Mar 2013, 17:22
Jayenkai
Too true! It's quite good at giving specific line numbers, though. The lines given are the currently running function, going bottom to top. If you GOTO the topmost line, that's usually where your bug is.

-=-=-
''Load, Next List!''
Tue, 19 Mar 2013, 13:58
Cower
Also, Xcode's debugger UI (sits on top of LLDB these days) is pretty good at what it does. Not the best, but pretty good.

At any rate, using languages with mediocre support is likely to get you mediocre error messages, so that's nothing new. You really ought to just use C++11.
Wed, 20 Mar 2013, 02:06
Afr0
At any rate, using languages with mediocre support is likely to get you mediocre error messages, so that's nothing new.


Quoted for truth!

-=-=-
Afr0 Games

Project Dollhouse on Github - Please fork!
Wed, 20 Mar 2013, 08:42
9572AD
I can't deal with eleventy billion libraries that all do different bits and pieces of the same things in slightly different ways. I have no critera with which to choose one and therefore can never make a decision.
Hence my use of "kit" languages rather than C++.

-=-=-
All the raw, animal magnetism of a rutabaga.