#32 Restore some of the BWB.*$ variables and add some

Open
opened 2 years ago by ChipMaster · 0 comments

There were BWB.* variables to set some of the OPTIONs, prior to v3. It would be good to get these back as constants so a program can examine its environment. OPTION would still set the value and perform sanity checks.

We should also add some:

  1. Current value of OPTION VERSION.

  2. The version number of bwBASIC. Maybe present it as two things:

    1. Textual version as seen on the splash
    2. A 1 based integer release counter, like has become prevalent in many places like Android. Hmmm.... how many releases have there been...

@KenUnix suggested this and @ChipMaster seconded. :-D

There were BWB.\* variables to set some of the OPTIONs, prior to v3. It would be good to get these back as constants so a program can examine its environment. `OPTION` would still set the value and perform sanity checks. We should also add some: 1. Current value of `OPTION VERSION`. 2. The version number of bwBASIC. Maybe present it as two things: 1. Textual version as seen on the splash 2. A 1 based integer release counter, like has become prevalent in many places like Android. Hmmm.... how many releases have there been... @KenUnix suggested this and @ChipMaster seconded. :-D
ChipMaster added the
enhancement
label 2 years ago
ChipMaster changed title from Where did the BWB.*$ variables go? to Restore some of the BWB.*$ variables and add some 2 years ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.