![]() |
Forum Index : Microcontroller and PC projects : CMM2: firmware extensions required to support a custom shell
Author | Message | ||||
thwill![]() Guru ![]() Joined: 16/09/2019 Location: United KingdomPosts: 4311 |
Apologies, despite my best efforts I've been thinking about this: 1. A mechanism to identify a custom shell program; either an OPTION or a named file in a fixed location, e.g. a file called SHELL.BAS in the root. 2. A program that exits via END or Ctrl-C automatically executes the shell program when it returns to the BASIC command line. 3. An alternative to Ctrl-C, e.g. Ctrl-X which returns to the BASIC command line and does not execute any shell program. 4. An extension to the END keyword that mean exit to BASIC without executing the shell program. 5. An extension to ON ERROR to allow a program to control whether it should exit to BASIC or execute the shell program - in the latter case MM.ERRNO and MM.ERRMSG$ would ideally be written to a file in a known location, e.g. a file called ERROR in the root, or somehow passed in on the MM.CMDLINE$ of the shell program. I don't suppose there is any possibility of this in the future ? Tom Edited 2020-10-16 22:02 by thwill MMBasic for Linux, Game*Mite, CMM2 Welcome Tape, Creaky old text adventures |
||||
matherp Guru ![]() Joined: 11/12/2012 Location: United KingdomPosts: 10315 |
I assume this is a joke and will treat it as such |
||||
thwill![]() Guru ![]() Joined: 16/09/2019 Location: United KingdomPosts: 4311 |
That would be a "No" then ![]() MMBasic for Linux, Game*Mite, CMM2 Welcome Tape, Creaky old text adventures |
||||
![]() |
![]() |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |