andrew/akbasic
1
0
Fork 0
Code Issues 27 Pull Requests Actions Packages Projects Releases Wiki Activity

Two lines carrying the same written line number silently keep the last #11

New Issue
Open
opened 2026-08-02 19:04:17 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 19:04:17 -04:00
Collaborator
Copy Link

Source: TODO.md §6 item 28 (at 9151438)

akbasic_runtime_file_line() refuses a collision that involves an assigned number, but leaves
numbered-onto-numbered alone -- which is what a file with 10 PRINT "A" twice has always done.

A duplicate in a hand-written file is a mistake rather than an intent, and refusing it would be
consistent with the other three cases.

Not changed with the rest because it is the one collision that can appear in an existing
program, so it carries corpus risk the others do not: 41 reference cases and 22 local ones would
all have to be shown clean first. src/runtime.c, in the FAIL_NONZERO_RETURN that already names
the slot.

Files: src/runtime.c (akbasic_runtime_file_line)

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §6 item 28 (at 9151438) `akbasic_runtime_file_line()` refuses a collision that involves an *assigned* number, but leaves numbered-onto-numbered alone -- which is what a file with `10 PRINT "A"` twice has always done. **A duplicate in a hand-written file is a mistake rather than an intent**, and refusing it would be consistent with the other three cases. **Not changed with the rest because it is the one collision that can appear in an existing program**, so it carries corpus risk the others do not: 41 reference cases and 22 local ones would all have to be shown clean first. `src/runtime.c`, in the `FAIL_NONZERO_RETURN` that already names the slot. **Files:** `src/runtime.c` (`akbasic_runtime_file_line`) --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 0.1.x milestone 2026-08-02 19:04:17 -04:00
tachikoma added the defectblast-radius:lowstatus::grooming labels 2026-08-02 19:04:17 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:low defect status::grooming
Milestone
No items
No Milestone 0.1.x
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/akbasic#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?