Embedded Basic can be compiled for three different platforms.
1) Telnet interface for the spinneret
2) PST interface to PC
3) Stand-alone PS/2 keyboard and TV output
All three are the same except for the INPUT and OUTPUT methods. All run on a single propeller chip.
What is missing and a way to get programs in-to and out-of the development environment. Possible a PST type program that can record and playback would work for the PST version.
What I really mean to say is how many instances of EmbeddedBasic can load and run into a single Propeller chip all at the same time? For example, if it takes up 2 cogs, then four instances could run at the same time.
@David, There is 4K for the BASIC program (vars are stored in a seperate area). Using the EEPROM would be really slow with GOTO having to search for the line number, it would mean a different program structure would be needed (like labels instead of line #s).
Humanoido, It is only setup to run as 1 instance, but could probably be modified to run multiple. If we (the propeller community) want to create a serious embedded BASIC, then it should be well thought-out and documented (my embedded basic was just a "can it be done" project and is NOT well thought-out or documented).
In one of posts before I referenced to MY post in another thread that I wrote ON Line number search to improve speed on read directly from SPI/I2C devices. BUT Now I think You not readed it at all.
Bad but it is You that decide what You will use.
@David, There is 4K for the BASIC program (vars are stored in a seperate area). Using the EEPROM would be really slow with GOTO having to search for the line number, it would mean a different program structure would be needed (like labels instead of line #s).
Humanoido, It is only setup to run as 1 instance, but could probably be modified to run multiple. If we (the propeller community) want to create a serious embedded BASIC, then it should be well thought-out and documented (my embedded basic was just a "can it be done" project and is NOT well thought-out or documented).
@David, There is 4K for the BASIC program (vars are stored in a seperate area). Using the EEPROM would be really slow with GOTO having to search for the line number, it would mean a different program structure would be needed (like labels instead of line #s).
Why not just build a line number to source program offset translation table to speed up GOTO and GOSUB? When the user types RUN you could first scan the entire program for GOTO and GOSUB statements and remember the target line numbers. Then make a second pass looking for those numbers and remembering their source code offsets. After that, GOTO and GOSUB could just use that table to find their target lines with no searching.
Humanoido
Posts: 5,770
Comments
1) Telnet interface for the spinneret
2) PST interface to PC
3) Stand-alone PS/2 keyboard and TV output
All three are the same except for the INPUT and OUTPUT methods. All run on a single propeller chip.
What is missing and a way to get programs in-to and out-of the development environment. Possible a PST type program that can record and playback would work for the PST version.
Bean
Humanoido, It is only setup to run as 1 instance, but could probably be modified to run multiple. If we (the propeller community) want to create a serious embedded BASIC, then it should be well thought-out and documented (my embedded basic was just a "can it be done" project and is NOT well thought-out or documented).
Bean
In one of posts before I referenced to MY post in another thread that I wrote ON Line number search to improve speed on read directly from SPI/I2C devices. BUT Now I think You not readed it at all.
Bad but it is You that decide what You will use.