This is a cache of https://vccplus.brianholman.com/vcc-plus/basic/. It is a snapshot of the page as it appeared on 2026-11-21T00:00:40.492+0000.
BASIC with a modern workbench · VCC Plus
← VCC Plus product guide

Inside VCC Plus / BASIC Development

BASIC with a modern workbench

Keep the immediate reply of a BASIC prompt. Add a native source editor, statement stepping, variables, recoverable documents and a path onto disk or tape.

Two views of the same program

A BASIC program can begin at the green screen: type a numbered line, press Return, and ask the CoCo to list or run it. That remains a useful way to learn. As a listing grows, you may want a Mac document you can search, revise, compare and save without retyping lines into the machine.

Develop → BASIC Development… provides that workspace. Its source document belongs to the Mac. The program loaded into the CoCo belongs to guest memory. The two can start with the same listing and then diverge as you edit. VCC Plus makes transfer an explicit action so a small source edit does not unexpectedly replace a program already running.

Choose Read from CoCo at the BASIC prompt to bring the guest listing into the editor. Save it as a Mac source document. In the other direction, Load into CoCo sends the numbered listing to the machine and leaves BASIC ready. Run transfers it and starts it. Direct loading supports the BASIC prompts in Disk BASIC, Hard Drive BASIC and CoCo SDC. Stop a running guest program with CoCo Break before replacing it.

The official VCC Plus BASIC editor with the Earth or Mars example

A source editor for numbered lines

Start with New or open an existing source file. Numbered BASIC is still numbered BASIC: a line number gives a statement its place in the program, and branches can refer to those numbers. The editor helps you manage that structure while preserving the language you are learning.

Use Check Source to find a problem before transfer. Go to Line… moves to a numbered line. Renumber… changes line numbers and recognized references together, useful when a once-small program needs room for another branch or a new subroutine. Read the result before running it, especially if the listing uses unusual techniques.

Keyword suggestions let Tab complete a faint proposed ending. They save typing without hiding the BASIC command that will execute. Keep a reference alongside the editor when a keyword is unfamiliar: understanding the difference between a printed string and a variable is more useful than accepting a completion by habit.

All three language editors support Find in File. Command-F searches; Command-G goes to the next occurrence and Shift-Command-G goes back. Match Case can narrow the search. Select text and use Command-E to make that selection the search term. Option-Command-F opens replacement. A file-wide replacement is one Undo operation, so you can inspect its effect and reverse it together.

A phrase in a comment or quoted message can match the same search as program logic. Check the match count and the selected occurrence before replacing every match. Editing source changes the Mac document; the CoCo keeps its current program until you transfer another version.

Run a small prediction

Here is a useful first listing to type into a practice document:

10 FOR N=1 TO 5
20 PRINT N
30 NEXT N
40 END

Before running, predict the first number, the last number and the number of printed lines. Choose Run, review any replacement confirmation and give the CoCo display keyboard focus if it asks for input. Now change the upper limit to three in the source document. The running machine does not change simply because the editor text changed. Run the revised listing to test the new prediction.

This distinction becomes particularly valuable when experimenting with an assistant. You can discuss and review a draft while the last approved program remains in the machine. A proposed improvement and a demonstrated improvement are separate stages.

Stop before a BASIC statement

A breakpoint answers a concrete question: what are the values just before this statement executes? Set a stop beside a numbered line and run to it. The debugger’s highlighted position tells you where the program is paused. A value you inspect there belongs to that moment, not to a prediction of what the highlighted statement is about to do.

Continue runs toward the next stop. Step Into advances a statement and follows a BASIC subroutine. Step Over lets a subroutine finish so you can examine its effect from the calling code. Step Out returns toward the caller. These are language-level operations; a single BASIC statement can require many CPU instructions.

Use Variables to inspect the values available at the stop, or add a particular name under Watches so it is easy to find again. A loop counter, a string holding a player’s answer and a score are useful first choices. Compare a value before and after the statement you suspect. That is often faster than adding PRINT statements everywhere and trying to catch fast-moving output.

Source debugging depends on a supported BASIC environment and recognizable interpreter state. When a value is unavailable, treat it as unavailable. The machine debugger provides a different level of inspection when you need registers, addresses or instructions.

Keep the listing, keep the result

Saving a Mac source document preserves the text. Saving a BASIC program to a guest disk or cassette preserves a guest-format copy. Neither automatically includes the current values of every running variable. Decide which kind of copy you need before a restart.

The file actions beside Save can export a disk or cassette. The export dialog tells you which command to use inside the CoCo, avoiding the guesswork of remembering whether a particular artifact should be loaded as BASIC or as machine code. Disk export can include a DOS bootloader for a disk you want to start with DOS.

A source file is a convenient place to edit tomorrow. A disk image is a convenient way to put the program among other CoCo files, test the loading process or move it toward compatible real hardware. The media guide explains the working-copy and mounted-disk safeguards.

Examples without losing your own work

The installed books and quick reference give you places to open small programs. Reviewed BASIC examples from selected Archive Library pages open in their own BASIC Example workspace. Opening one does not silently replace your main source document or execute it in the guest.

Read the example, check its required environment and save an editable copy when you want to develop it. Load into CoCo and Run remain explicit actions, with the normal safeguards before replacing unrelated guest work. Reopening a reviewed example can return to its own edited or recovered draft.

For your first web lesson, try Your first program. For the deeper in-app path, choose Programming in CoCo BASIC from the Manual Library. When you want help with a particular change, the AI coding guide explains how to share this BASIC document without sharing every open project.

Your next discovery

Choose the next part of your workbench.

Explore the machine, the development tools, and the books that connect them.

Back to the product guide
A closer look

Open original