Skip to content

About the interpreter #3

Description

@LdBeth

Now we have a lambda rep based interpretation, however it is buggy and limited in certain ways:

  • It doesn't implement runtime I/O, and because the type checker requires top-level to be integer, it can only do integer arithmetic.

  • It can't even do integer arithmetic right, because the design represents integer as even number Int32 so it can be distinguished from pointers, which uses odd number Int32, and the the convention's done at parsing time, but the lambda interpreter is written for regular integers.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions