[M3devel] Why do we need external debugging?

[Daniel Alejandro Benavides D.]

Hi all:
yes, the VAX900 mainframe had this capability, of executing the code an same time verifying its operation results.
Would like to make a RT in that way, but it shouldn't be that hard, should be?
Thanks in advance

PS: BTW I just had an idea today, make the experiment in DEC-SRC of DISPOSABLE memory information safe, so making some adjustments to the type system, with coercion and other soft typing stuff make the language type safe entirely,
We would need just suppress the annoying word UNSAFE of all modules, and make the language 100% machine checkable.
At the same time introducing functional objects, like in bay Modula-3 , to able to model the language in that way.

Thanks in advance



--- El lun, 1/4/13, Darko <darko at darko.org> escribió:

De: Darko <darko at darko.org>
Asunto: [M3devel] Why do we need external debugging?
Para: "m3devel developers" <m3devel at elegosoft.com>
Fecha: lunes, 1 de abril, 2013 16:53

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/237cc323/attachment-0002.html>