[M3devel] Why do we need external debugging?

[Jay K]

External debuggers are good. Have you used Visual Studio much?
Generate the right debug information and we get excellent working debuggers that people put a lot of time and work into.


On the other hand, I do understand your notion of "internal debugger" and agree it is a good approach.


 - Jay



> From: darko at darko.org
> Date: Mon, 1 Apr 2013 14:53:37 -0700
> To: m3devel at elegosoft.com
> Subject: [M3devel] Why do we need external debugging?
> 
> The last time I used an external or lowish-level debugger was the last time I programmed in a language other than M3. I find the language so safe and reliable that I don't quite understand the need for external debuggers. Is it driven by a need to integrate with other languages or external libraries?
> 
> Why can't a debugger be optionally compiled into the code and supported by the runtime? I find I don't need much more than the ability to log procedure execution, procedure parameters and local variables. I imagine some sort of debugging mode with a simple command line and an interrupt mechanism would facilitate interactive debugging.
> 
> Am I the only one who thinks this?
> 
> - Darko
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20130402/eeec11f3/attachment-0002.html>