DDT and DeskDebug
Mr John FO Evans
grave disservice by asking for the moon.
If any new programs are to emerge new talent us needed which in turn will
need a straightforward development environment which works over the range of
new RISC OS hardware. What is not needed is a stalling of any updating of
the working enviroment by asking for something which works with all the
latest programming gizmos. OK they may be available on the latest Linux or
Windows super-box - but they are most unlikely to become available under
RISCOS given the current climate.
So why are we not getting the minimum - which is DDT and/or DeskDebug under
RISCOS 4,5 and 6? Together with some upgrades to unplug some of their
current problems ?
Reading Archive I would suggest that C++ is far from a standard build under
RISCOS so why not settle for Assembler and C?
RISCOS development thrived on part-time programmers with good ideas but who
were not necessarily computer scientists.
Lets try to get some of them back.
John
--
_ _________________________________________
/ \._._ |_ _ _ /' Orpheus Internet Services
\_/| |_)| |(/_|_|_> / 'Internet for Everyone'
_______ | ___________./ http://www.orpheusinternet.co.uk
Steve Potts
Mr John FO Evans <mi...@orpheusmail.co.uk> wrote:
> In my opinion many of the correspondants on this topic are doing RISCOS a
> grave disservice by asking for the moon.
>
> If any new programs are to emerge new talent us needed which in turn will
> need a straightforward development environment which works over the range
> of new RISC OS hardware. What is not needed is a stalling of any updating
> of the working enviroment by asking for something which works with all the
> latest programming gizmos. OK they may be available on the latest Linux or
> Windows super-box - but they are most unlikely to become available under
> RISCOS given the current climate.
>
> So why are we not getting the minimum - which is DDT and/or DeskDebug under
> RISCOS 4,5 and 6? Together with some upgrades to unplug some of their
> current problems ?
I have heard in the past that DDT is created containing knowledge about the
operating system version at which it is targeted, to enable it to do some low
level stuff for it to work at all. This implies that any significant changes
to the core RISC OS mean a rebuild / recoding??? of DDT.
Although I've used DDT in the past (and been limted by it), I don't
understand how it does what it does.
[snip]
Steve.
--
StevePotts at blastzone DOT demon STOP co DOT uk (www.blastzone.demon.co.uk/)
Written on RISC OS.
http://www.riscos.com/
druck
> Although I've used DDT in the past (and been limted by it), I don't
> understand how it does what it does.
I suspect neither does anyone else anymore, hense why it doesn't work on
later OSs.
---druck
Martin Wuerthner
druck <ne...@druck.org.uk> wrote:
I do not think that is the problem. The problem is that there is no
overlap between the people who know about RO6 and have the RO6 source
code and the people who know about DDT and have the DDT source code.
DDT should be fairly straightforward to sort out for anyone having
access to both source trees. Most of it would be about adapting a few
hardwired memory addresses and using some of the more recent system
calls rather than accessing OS information directly.
At a guess, adapting DDT for RO6 is an order of magnitude easier than
it was to adapt it for RO5.
In comparison, it should be fairly trivial to get DeskDebug running on
RO6. Again, much easier than it was to get it running on RO5, but as
far as I know Niklaus does not have access to a machine with RO6.
Martin
--
---------------------------------------------------------------------
Martin Wuerthner MW Software http://www.mw-software.com/
ArtWorks 2 -- Designing stunning graphics has never been easier
spam...@mw-software.com [replace "spamtrap" by "info" to reply]