Appears to be fixes, probably related to processor state transitions (blind guess).
… I’ve already updated my sdk according to their instructions and my Machikania build is using that.
btw after writing a few programs on it, I’m having doubts about syntax highlighting now: the terse nature of one-character-variables made it so that more color would probably distract.
edit: okay my doubts are cleared after knowing that you can usevar and useclass.
Actually, there are two modes of MachiKania type P: OS mode and editor mode that correspond to phyllosoma.uf2 and phyllosoma_kb.uf2, respectively.
To use the OS mode, tactile switch buttons are required, which do not exist in PicoCalc. So, only the editor mode is supported so far. I will think about selecting the OS mode in PicoCalc in addition to editor mode.
About the build and pico SDK, I don’t have any idea about PicoMite. We always check the newest version of SDK for building MachiKania. So far, SDK 2.1.1 is confirmed for building the newest version of MachiKania.
This feature will enable a lot of OS-like scenarios.
Maybe this is a far reach, but I’m imagining that, with a load instruction, one could write dos “memory reservation” style routines and setup calling conventions between chainloaded programs.
Before load, the system saves the entire ram image of the running program, registers and BASIC vm states (e.g. g_vars_mem, tvmem, graphical buffer) somewhere – sdcard for example.
The load instruction can also supply arguments for the new program, which can be later retrieved with the system instruction
If a program exits, it can have a return value, which can be retrieved with the system instruction by the caller when the machine states are restored.
With these infrastructure, one can boot into a custom shell written in basic, use an editor written in basic etc. and ultimately have an extensive “userland” in basic.
I see. Now I understand what the “LOAD” in your previous comment means.
It’s a challenge. I need to reconsider the compiler. It will be another level, and probably I need to start from scratch for it.
I’m also considering the next version of KM-BASIC (used in MachiKania), that will be for any CPU but not only for ARM. I will consider what you say here. Please wait me for 3-5 years…
This is indeed a far reach. I can first pick up a more “basic” task to get familiar with the codebase
Another suggestion: add DIM xxx AS type – after that, one does not need to append the type moniker after the variable name.
Perhaps this goes against the language design, but I truly feel the urge to have this when I dump 3DWAVE.bas by hand on the picocalc keyboard – I have to keep shift pressed down so as to input # more easily.
I also considered such definition for string/float variables, but found that the language syntax would lose consistency; SIN#(…), COS#(…), etc will remain with “#”. Removing all “#” from float function would make the language syntax more complicated.
Thank you very much for the suggestion and hint/help to improve MachiKania BASIC.
The current production branch of GitHub repository supports the coloring in editor. Comments, reserved words, and strings are colored green, blue, and red, respectively.
I am using the multiboot bin version provided in the first post of this thread and it does not have coloring in the editor. Can you release a newer bin with coloring in the editor?
I can build the uf2 from source but I don’t know how to make a bin file that will work with multiboot.
I also don’t know how to make the “bin” file for multiboot. Can someone provide the way to do that (link or brief explanation)?
I got it by following the case of MicroPython. I will consider to include the bin file in the official release. Until the official release, please download it here: (phyllosoma_kb.bin).
Are there two versions of bootloade for Pico and Pico 2? Or, only for Pico 1?
By the way, the release of an official version of MachiKania for PicoCalc is on the way. I will be published in 2-3 weeks.
Don’t worry about supporting multiboot, it’ll be completely obsolete fairly soon (same timeframe as your main release, a couple of weeks.) If there is any need for bootloader support after that I’m happy to help implement it.
I see. Thank you. I will provide the bin version of MachiKania after the official release of bootloader. Probably, I understood how to make the bin file for this purpose.
The bottom line of “F1-LOAD”, “F2-SAVE”, and “F4-RUN” is modification by guu. The “LOAD”, “SAVE” and “RUN” are our original ones. The F1, F2, and F4 keys still work.
Thank you for suggesting the auto-completion in the editor. However, as I stated previously on July 5th, the MachiKania community is still small, and unfortunately, we are not in a position to accommodate large-scale pull requests at this time. I briefly saw your pull request, but we couldn’t pull it as we need to keep the stability of MachiKania for all implementations (the next release will contain 68 *.uf2 files).
Again, I appreciate your suggestion to improve MachiKania.
