-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPTION BASE should be allowed after ERASEing all arrays #185
Labels
Comments
Wow, I'd put this in the "rather obscure" category, for sure. I can't help wondering how on earth you found this one. :) |
As almost always, by accident... Though in the context of issue #182 it's not quite so random. |
I had missed #182. But yes, I do see the connection now. |
robhagemans
added a commit
that referenced
this issue
Jun 30, 2022
robhagemans
added a commit
that referenced
this issue
Jun 30, 2022
Fixed by commit e261100 |
As almost always, by accident... Though in the context of issue #182 it's
not quite so random.
…On Thu, 23 Jun 2022, 09:56 Rutger van Bergen, ***@***.***> wrote:
Wow, I'd put this in the "rather obscure" category, for sure. I can't help
wondering how on earth you found this one. :)
—
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB25REXGTX3AQRW5HLW4FW3VQQRDFANCNFSM5ZROFEYA>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test code:
What happens:
What should happen:
Background -
OPTION BASE
should fail withDuplicate Definition
if there are allocated arrays. However, if all arrays have beenERASE
d it should be allowed. PC-BASIC disallows it if at any point an array has been allocatedThe text was updated successfully, but these errors were encountered: