Richard Russell's BBC BASIC
Pages: 1 2
Steffen Huber (91) 1953 posts |
Not sure if it is the latest version of BasDT: Dick’s tools seem to have vanished from the Web. I remember looking for TemplEd recently, and only found it in DrWimp. |
Steve Drain (222) 1620 posts |
We are? I am pretty happy with the present state of affairs. ;-)
That looks very comprehensive, but why? I can already get all the information I need with Reporter.
If you are modifying BASIC itself there are still few unused locations just below |
Tristan M. (2946) 1039 posts |
That will do nicely for now. Thank you kindly. The new BASIC manual not being available in electronic format is a little irritating to me. Historically I prefer the permanence of books, however at this point in my life the convenience and ability to make backup copies of an electronic version far outweighs it. All that aside, Something with basic BASIC debugging support would be good. |
nemo (145) 2546 posts |
|
nemo (145) 2546 posts |
Thanks Steffen! |
Steve Drain (222) 1620 posts |
Have you looked at what Reporter can do for you?
Yes, though Reporter does not support it directly it is simply implemented.
Yes
Yes
Not for you, I know, but it might be for the general pulic. ;-) |
Rick Murray (539) 13840 posts |
The “general public” would probably like tools like BASIC Spy, as the stuff available with BASIC’s CALL/USR R8-R12 are probably pretty incomprehensible for many. Just, as a throwaway… How would one simply, from assembler, call a BASIC function such as PRINT or INKEY? What about reading A%? What about a user PROC/FN? I’m quite sure all this is possible (and that Basalt does it…), but when reading through pages 229-241 of the BASIC manual, I think some examples are sorely missed. I recall the epic ring-bound BBC User Guide was so full of examples it was practically an interactive workbook (and set the standard for manuals, IMHBLIO). |
Steve Drain (222) 1620 posts |
It is not very friendly, but all the documentation is there in the manual. About a year ago I did have a go at making a way to use CALL etc more friendly, possibly using SWIs. This was based on the way Basalt does things. 1
If you were evaluating a expression in a string which included the function
Finding a variable is a combintion of
A I agree that the BBC User Guide was like a workbook, and I learned much from the equivalent Spectrum Manual. 1 Basalt was written using the facilites of Extended BASIC Assembler, which can only run 26-bit and with an old version of BASIC. I have almost eliminated 26-bit from my life, so assembling meant running up VRPC. As a consequence I have not been doing much with it lately. I can assemble under Aemulor, but there are insumountable problems with errors, because there is no BASICTrans anymore and the BASIC Messages are incompatible. I have been working on adapting the source for RO5, but there is a lot of it. ;-( 2 Any |
Alan Robertson (52) 420 posts |
Are there any developers out there who would like to work towards a new IDE, something along the lines of what Nemo suggested? Basic/C Visual Studio for RISC OS |
Jeffrey Lee (213) 6048 posts |
I don’t have the desire to create an IDE (much less one for BASIC), but one of the many things on my todo list is to update the Debugger module so that it’s capable of using the hardware breakpoints & watchpoints which have been available as standard since ~ARMv6. A SWI interface to allow debuggers to set breakpoints (with associated handler code) should be a useful feature for debugging many programming languages. |
Alan Robertson (52) 420 posts |
I agree. That would be VERY useful to have. |
Dave Higton (1515) 3526 posts |
I used Visual Studio for several years prior to retirement. It always struck me how much screen space it wastes on stuff that you don’t need to see in the particular phase you’re working on. For example, when you’re editng a file, you don’t need to see the source tree or the build results. That screen space would be a valuable addition to the editor window’s size. As we all know, we never have enough pixels on the screen. So, if we ever did integrate the stages of code edit/build/test/debug, let’s see if we can devise a better way. Would it be good to have a hot key to the central control window, and all tasks chosen from there (edit, build, debugger, etc.) simply jump to the front as and when they are run? Instead of the source files currently being edited appearing as tabs, should they appear more like a menu? Tabs only work successfully for a small number, because they’re wide but not tall, which suggests to me that they’re better stacked vertically rather than disappearing off to the right or left when you’ve got a lot of source files open. Offered in the spirit of wanting to start a discussion on what would do the job well, rather than copying what’s out there already. |
Jan-Jaap van der Geer (123) 63 posts |
Whilst I agree with that not being necessary to see all the time, as a VS user in my professional life, I don’t recognise what you’re saying. In VS you can just dock the Solution Explorer to the side, it expands when your mouse hovers over it (or pressing Alt-Shift-L I suppose, although having widescreen I usually actually leave it open all the time). The build results also open while compiling and is otherwise closed. I think all these things have been like that since I started using VS with VS2005. I’d much rather have intellisense than an IDE though (although I suppose you pretty much need an IDE to implement some form of intellisense) |
Tristan M. (2946) 1039 posts |
Here we have one of the many reasons I refuse to use anything based off Eclipse. I don’t think it fits on anything less than a super HD video wall. IIRC I got Motor to build for RO ages ago but that’s just a terminal IDE. |
nemo (145) 2546 posts |
My VS setup is two monitors wide. Left for code, right for everything else. But I’m an untidy-pile-of-windows not a one-tab-at-a-time guy. |
Steffen Huber (91) 1953 posts |
I work with Eclipse on two 24" 1920×1200 screens for years now. It has its weaknesses, but it is also very flexible with its docking framework. It is hard to think of a better way to provide the flexibility of its views and perspectives. At home, I now have one 28" 4K screen, which is really a completely different world when it comes to “available screen space”, no matter if Windows, Linux or RISC OS. However, it makes RISC OS’ non-keyboard-controllable philosophy sometimes difficult to love, because the distance of mouse travel basically explodes. It needs a different working style. Speaking of IDEs, I am not going to create one, but I think that we could really do with some modern VCS stuff on RISC OS. Maybe a generic client with a backend on a Linux slave doing the hard work? |
Jeffrey Lee (213) 6048 posts |
AKA a network share for accessing the files and a VNC/SSH session for interacting with the source control client? |
Tristan M. (2946) 1039 posts |
Ie what myself and many others do. My thinking is probably sideways on this, but what would be neat is a kind of specific filesystem translation layer. Like how !SVN can parse source trees to / from a more POSIX compatible format, but freestanding so other things like Git for example could use it as a kind of shim. Or something. |
nemo (145) 2546 posts |
My solution is an emulator running on Windows with Google Drive (which does version control of every single file). This isn’t proper version control, of course. I’ve not experimented with using hg on the HostFS files, that might work. I wrote an FS decades ago called LayerFS, which merged directories together with a single writeable one (much like Windows Seven’s ‘libraries’). It was intended to allow old files to be moved to CD, yet still appear to be available (accessing them produced an “Insert disc ‘CD12345’” prompt). But it worked for source code too – adding a new writeable directory to the list was a commit, in effect. |
Steffen Huber (91) 1953 posts |
I think that we could really do with some modern VCS stuff on RISC OS. Maybe a generic client with a backend on a Linux slave doing the hard work? This is one option, using an IDE on Linux or Windows to do everything except testing (and possibly compiling in my case of GNAT) another. However, a native solution could be much neater – after all, it feels like the “use VNC/RDP to access a capable browser” solution. Just not right. |
Pages: 1 2