s_jekutsch (02/07/91)
Compared (for example) with Turbo Pascal the Acorn ANSI-C-Compiler (and any other compiler, too) is lacking the programming environment, which makes it easy to use (Editor-Compiler-Linker-Debugger together in the desktop with windows, icons and hot-keys). There is no support for it. I don't think that the !Edit-TaskWindow is enough. But - as I see - many people are developing many good applications. Which programming environment are you using? Twin? Or a selfmade utility? Or are you developing your software for the archimedes with a PC :-) ? What solutions do you have? I hope that many of you post about it (or mail me). I am curious. Seba s_jekutsch@irav1.ira.uka.de
gavinw@syma.sussex.ac.uk (Gavin Wraith) (02/11/91)
> other compiler, too) is lacking the programming environment, which makes it > easy to use (Editor-Compiler-Linker-Debugger together in the desktop with > windows, icons and hot-keys). There is no support for it. I don't think that > the !Edit-TaskWindow is enough. But - as I see - many people are developing > many good applications. Which programming environment are you using? Twin? Or > a selfmade utility? Or are you developing your software for the archimedes with > a PC :-) ? What solutions do you have? I hope that many of you post about it > (or mail me). I am curious. > > Seba > s_jekutsch@irav1.ira.uka.de I am not sure what the problem is. I use !Edit and a tiny Obey file !make to click on. I agree that the debugger is not very satisfactory for use with with programs that spend most of the time executing RiscOSLib functions. Incidentally, there seems to be a bug in res_openfile in Ansi C, version 3, RiscOSLib. It appends a "1" to the end of its filename argument. It is easily circumvented by using the system variable "Application$Dir", or whatever, directly with fopen in stdio.h. --- Gavin Wraith