SHORT Re: Suggestion: "fix" assert(obj)

[Jascha Wetzel]

Ary Manzana wrote:
> You'll waste less time to fix the bug if you know which is the line that 
> causes trouble, instead of doing these three steps: compiling with 
> symbolic debug info, launching the program again and see where it crashes.
> 
> You could even fix the bug by just looking at line 178, without debugging.

there is no way how access violations can have line numbers without 
adding debug symbols (read: line numbers) to the executable.
imho, using -g should be default during development and testing.