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

[Ary Manzana]

But, anyways, an "Assert failed in line 178" is much more informative 
than "Program segfault".

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.

Walter Bright escribió:
> sambeau wrote:
>> While I get your point completely I believe this style of debugging is 
>> only really useful to the hard-core professional.
>>
>> For the novice, where the debugger is a scary place of last resort, it 
>> would be more useful to have an assert too. All most of us want is a 
>> line number: and segfaults don't give us that.
> 
> They do when combined with symbolic debug info - that is how the 
> debugger is able to display your source code with the highlighted line 
> where it seg faulted.