Jump to content

BruceMcF

Members
  • Content Count

    245
  • Joined

  • Last visited

  • Days Won

    8

BruceMcF last won the day on September 12

BruceMcF had the most liked content!

Community Reputation

147 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, the ambiguity is layers of WHAT ... layers of routing, or layers of board. Either one or two layers of traces/routing only need one layer of board, 3 layers of traces/routing needs two layers of board.
  2. BruceMcF

    X16?

    It has a 16bit address space, over which your command Xtends.
  3. Though not ever use for a reentrant function can be handled by a loop. However, if there is a specific "reentrant" call option, it could push the current parameters onto a frame stack and pop them when done, so calls that don't need re-entrance don't have to pay the overhead.
  4. I haven't seen anything since the response on FB about when the next "movie" (ie, video) would be out and the mention that they are still working on getting it booting up, followed, of course, by a series of "turn it off and turn it back on" jokes.
  5. QBasic (two steps after the CBM V2 generation of Microsoft Basic) has variables that are local to procedures and subroutines. However, I do not know whether there was a local variable stack, or whether that was just a private namespace. On approach is to have a distinct recurse() function which copies the functions current local variables to a frame stack, uses the local variables for the call, gets the return value, and then copies the local variables from the frame stack. So then code that wants to pay the cost of re-entrant code can do so, without forcing all code to pay that cost.
  6. OK, let me get out the rulebook, and check if you broke any server rules. Hmmm, interesting, yes, ah, I didn't realize that a University has to charge the cost of the training table at ... WAIT A MINUTE, THIS THE THE NCAA DIVISION I MANUAL. It's not the server rulebook AT ALL!!! Guess I don't actually own a copy of the rulebook after all ... and even if I did, I would not be in a position to decide who had broken what rule!!! .... but my best guess is it's all cool. If you want to play with Forth as well as Basic, feel free to check out the xForth in the downloads section ... it has "Try it Now" enable.
  7. This gets into the associative arrays discussion from 2019. It's pretty clean to have a RAM disk on a specific device number, but for best utility it should emulate a drive. Typically we can equate file# and secondary address#, as for reading and writing sequentially they have to be between 2 and 14 and have to be unique, so the access to the RAM disk should permit that. We already have the vectored hooks for the device# I/O, so it can be prototyped as a Golden RAM ($400-$7FF) utility and if it works out, we could look at packaging it for addition to the Kernel. As a RAM disk, we have a lot of flexibility about set up information, because that can be in the commands that can be sent to the pseudo disk drive, so there is no need to strain to get information into the dev#, file#, sa# data. There is a very strong case to have the routines that OPERATE the a HighRAM RAMdisk in FlashROM somewhere, because placing it in High RAM requires a lot of trampolining, which would slow it down substantially, while LowRAM is quite scarce relative to HighRAM OR FlashROM.
  8. Most excellent. I will have a try of the new version sometime this weekend, as it is a holiday weekend (National Week Holiday) in Beijing, but this sounds like most everything I need from a general system text editor for Forth scripts.
  9. Precisely. This project worked hard to get the license, and it was a great relief when it came through. @Anshul3: There are lots of projects to emulate the C64, and this one is not aimed at treading over that same ground. Instead, it is aimed at giving people the EXPERIENCE of programming and working with an 8bit system without all of the inconveniences that were a result of the costs of things we take for granted today: just for one example, in the 1980's, mass storage as fast as flash storage on SD cards would have cost many thousands of dollars.
  10. According to translate google, that says: QUOTE Hello from Cali, Colombia I love retro computing, and more this project that is low cost, I have experience in basic and assembler programming and I like to collect old electronic equipment, I am in a project to create a 4-bit ALU using only transistors to complete a simple microcomputer with TTL logic. I saw David's video about the X-16 Commander and I really liked it, I'm going to download the emulator, to test it, I'm looking forward to the full development of this project UNQUOTE My Spanish is terribly rusty, but I think that is not far off. Great to have experienced Basic and Assembler language programmers on board!!!
  11. It might be mp3's and a command line tool to convert mp3's to wav files ends up a more compact package in a zip ... since mp3 is lossy compression, it might beat zip at compressing wav files to cover the size of the converter.
  12. I am also much more enthusiastic about having it than making it ... but I am enthusiastic ENOUGH about having it that I may make a trip to Shenzhen in the gap between the two week Chinese New Year holiday and the start of semester to see about getting it made if nobody else is game.
  13. Note that the Basic Ready prompt is what should happen after a system reset ... at least until the power up options from the RTC NVRAM become available ... but it seems that what is going on is that a hardware reset will also reset the Bank register directly, so the reset routine doesn't have to do that itself. So the reset routine expects to be executed with the banks (both RAM and ROM) in their own reset state.
  14. Excellent. For command line entry, it will already take you through chapters 1 and 2 of Starting Forth. Starting Forth is (c) Forth Inc., and while they make it freely available at their site, they don't permit free redistribution. So get it online or PDF at: https://www.forth.com/starting-forth/
  15. Yes, that's the crux of it. We need some V2 Basic hackers to have a go at some of the proposals in Issues on GitHub, or it will not happen in RomBasic. xForth debugging took me straight through to the end of summer vacation, and learning the ins and outs of ca assembly isn't really going to happen in the middle of the Semester, so that's not going to be me. That is, not unless it is the associative arrays in High RAM as device 7, which is a Kernel level expansion that Basic can use, and so can be programmed in acme, otherwise I am just on the sidelines cheering. My number one extension I would cheer for is HDIM to allocate arrays within $A000-$BFFF, and then if you have a parallel data structure across multiple banks, simply change the bank and the arrays reference all the parallel data in that bank. Edit: It just occurred to me that USER() might be give an array fill from HighRAM routine, that's a second thing that could be attempted from Acme.
×
×
  • Create New...

Important Information

Please review our Terms of Use