ChipMaster
/
bwBASIC
1
0
Fork 0
Code Issues 22 Pull Requests 0 Releases 17 Wiki Activity
Labels Milestones
New Issue

#13 PRINT USING with multiple values is not handled correctly

Open
opened 2 years ago by ChipMaster · 1 comments
ChipMaster commented 2 years ago

Needs verification but doing somthing like PRINT UNSING "#"; X, "SOMETHING" doesn’t tab over from X to the next stop before printing “SOMETHING”.

Turns out all further values should be printed in accordance with the mask and they should all be numeric, throwing a type error if not. See 1st comment.

Needs verification but doing somthing like `PRINT UNSING "#"; X, "SOMETHING"` doesn't tab over from X to the next stop before printing "SOMETHING". Turns out all further values should be printed in accordance with the mask and they should all be numeric, throwing a type error if not. See 1st comment.
ChipMaster added the
blunder
label 2 years ago
ChipMaster self-assigned this 2 years ago
ChipMaster added the
question
label 2 years ago
ChipMaster commented 2 years ago
Owner

Tested in BASICA and found things I didn’t remember. Once PRINT USING is invoked all further variables on the PRINT line are required to be numbers, that are then formatted with the USING mask and spaced according to the mask.

The bwBASIC implementation doesn’t provide the correct functionality when compared to M$ BASIC. Other dialects?

Tested in `BASICA` and found things I didn't remember. Once `PRINT USING` is invoked all further variables on the `PRINT` line are required to be numbers, that are then formatted with the `USING` mask and spaced according to the mask. The bwBASIC implementation doesn't provide the correct functionality when compared to M$ BASIC. Other dialects?
ChipMaster changed title from PRINT comma after USING doesnt tab to PRINT USING with multiple values is not handled correctly 2 years ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Apply labels
Clear labels
blunder
Something is not working duplicate
This issue or pull request already exists enhancement
New feature help wanted
Need some help Maybe Fixed optimization question
More information is needed wontfix
This won't be fixed
No Label
blunder
duplicate
enhancement
help wanted
Maybe Fixed
optimization
question
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
 ChipMaster
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes