3
IAmAnIssue
126d

“a stack-based language where pointers are poisonous and the interpreter doesn't do a good job of remembering non-constant values”

Project Type
Existing open source project
Summary

“a stack-based language where pointers are poisonous and the interpreter doesn't do a good job of remembering non-constant values”

Description
I was bored one day, that’s all. “i have a great esolang idea: to call a function you must push a pointer onto the stack but the only way to get the pointer is through a conditional greater than and then even when you get the pointer you need to call unpoison on it because pointers are poisonous by default and dereferencing poisonous pointers segfaults” - Ghosty I didn’t implement the conditional part, but everything else is true to the plan. Poisonous pointers and all. Syntax and examples are available on the GitHub repo and esolang wiki page. I’m going to put this up here because 1. PublicityTM 2. Criticism What I do know about: - memory/stack is shared across all scripts run in the same process (global state). - parsed with regex because I’m evil - inconsistent errors when parsing loops (parse error on “end” without “while,” runtime error on “while” without “end”) - invalid syntax is ignored... except before the declaration of constants (it’s a feature, not a bug). - yes Play around with it, break it, and let me know what you think! PS: stdin related instructions are not implemented in the current release jar. Compile it yourself for stdin.
Tech Stack
Java, no external libs
Current Team Size
1
URL
Comments
  • 0
    @irene of course something already exists. Doesn't stop me from making my own 🙃
  • 0
    Some updates:
    - I built the new version of the interpreter so you don't have to
    - Excess interpreter output is suppressed unless you supply the --debug flag
    - [object Object]
Add Comment