Skip to content
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

Change left bound behavior #2

Open
jfioasd opened this issue May 31, 2023 · 0 comments
Open

Change left bound behavior #2

jfioasd opened this issue May 31, 2023 · 0 comments

Comments

@jfioasd
Copy link
Owner

jfioasd commented May 31, 2023

  • If IP goes over the left bound (not in a ? clause), the program halts.
  • In a ? clause, (facing left) the IP is used as a backwards index (like the current specs). This should make for golfier IP jumps between 2 loops. (Facing right for ? clause wraps around like the current right bound specs.)
  • I'll remove the condition in the ? since it's not used very often.

  • Step left 1 ({) is so common, why not make the IP start at an odd index (e.g. -1)? (this will invalidate my existing answer, change it to: ' L|qq'ol')
  • Add { and } to the language. Make $ to be conditional step left. e.g. : A$BC If IP+1 is $: IP += 1 if TOS.pop is falsy.

Maybe:

  • Implicitly run _ when popping from a stack without enough arguments?

Both _ and # are annoying boilerplate when writing programs.

The rest of the language is fine, I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant