issue#-187 adding a run-time debugger to BlackBox
Posted: Mon Jun 04, 2018 10:12 pm
This is a voting for adding a run-time debugger to BlackBox.
I am aware of the fact that a run-time debugger is rarely needed in BlackBox and that purists may even find it evil.
On the other side ominc developed one at least for internal use and ETH Oberon A2 also has one.
This shows that there are situations where a run-time debugger may actually be useful.
It could be argued that a run-time debugger should be provided as a CPC package. The problem is that the
consistency between the internal run-time data structures of BlackBox and the debugger cannot be guaranteed then.
The slightest change in BlackBox internals will break the debugger. The integration into the distribution
avoids this kind of inconsistencies.
Another argument is more marketing related.
Many people think that an IDE without a run-time debugger cannot be taken serious,
simply because they are used to it.
The proposed run-time debugger is based on the ominc version that has been ported to BlackBox 1.7 by X512, Ivan, etc.
I have adapted it to make it easier to use, localizable, documented, synchronized the changes with DevDebug in BlackBox 1.7.1 etc.
Nevertheless it is still a simple debugger consisting of 2 modules, one for attaching a debugger to the running BlackBox instance (DevDebugCmds)
and one for the run-time debugger (DevRTDebug). None of those modules is loaded unless it is really used, i.e. there is no
overhead involved and there are no incompatibilities introduced.
A test version is available from http://blackboxframework.org/unstable/i ... 1.1030.zip.
For the diffs see https://redmine.blackboxframework.org/p ... a4d9f1453b.
Gentlemen, please cast your vote or let me know if you think we need more discussion on this issue.
- Josef
I am aware of the fact that a run-time debugger is rarely needed in BlackBox and that purists may even find it evil.
On the other side ominc developed one at least for internal use and ETH Oberon A2 also has one.
This shows that there are situations where a run-time debugger may actually be useful.
It could be argued that a run-time debugger should be provided as a CPC package. The problem is that the
consistency between the internal run-time data structures of BlackBox and the debugger cannot be guaranteed then.
The slightest change in BlackBox internals will break the debugger. The integration into the distribution
avoids this kind of inconsistencies.
Another argument is more marketing related.
Many people think that an IDE without a run-time debugger cannot be taken serious,
simply because they are used to it.
The proposed run-time debugger is based on the ominc version that has been ported to BlackBox 1.7 by X512, Ivan, etc.
I have adapted it to make it easier to use, localizable, documented, synchronized the changes with DevDebug in BlackBox 1.7.1 etc.
Nevertheless it is still a simple debugger consisting of 2 modules, one for attaching a debugger to the running BlackBox instance (DevDebugCmds)
and one for the run-time debugger (DevRTDebug). None of those modules is loaded unless it is really used, i.e. there is no
overhead involved and there are no incompatibilities introduced.
A test version is available from http://blackboxframework.org/unstable/i ... 1.1030.zip.
For the diffs see https://redmine.blackboxframework.org/p ... a4d9f1453b.
Gentlemen, please cast your vote or let me know if you think we need more discussion on this issue.
- Josef