Skip to content

Parse scheme code properly #4

@turbopape

Description

@turbopape

As of now, I replace "problematic" scheme literals "#, @, etc..." using a dumb str replace. It would be nicer to have scheme parsed according to a proper scheme grammar and then use the generated structures for eval/apply. Maybe use instaparse?
Please head over to scheje.slack.com so we can discuss this further.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions