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

Parse scheme code properly #4

Open
turbopape opened this issue Mar 19, 2016 · 3 comments
Open

Parse scheme code properly #4

turbopape opened this issue Mar 19, 2016 · 3 comments

Comments

@turbopape
Copy link
Owner

turbopape commented Mar 19, 2016

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.

@emacstheviking
Copy link

emacstheviking commented Oct 8, 2016

Interested in helping but couldn't sign in to slack??! I've written lots of DCG parsers with Prolog for this and that and some parsers with Grako/Python. I am now using Clojure for my day job and looking to hone my skills elsewhere and this looks interesting as I have used scheme in the past as well. So, if you would like some assistance, here I am!
Thanks,
Sean.

@turbopape
Copy link
Owner Author

Hey, I would be more than happy to have you aboard!

You couldn't request a slack invite? Please share your email and I'll send
you an invite.
My email is: Rafik . Naccache @ Gmail . Com

Cheers,

Rafik

Le 8 oct. 2016 11:56 PM, "Sean Charles" notifications@github.com a écrit :

Interested in helping but couldn't sign in to slack??! I've written lots of
DCG parsers with Prolog for this and that parsers with Grako/Python. I am
now using Clojure for my day job and looking to hone my skills elsewhere
and this looks interesting as I have used scheme in the past as well. So,
if you would like some assistance, here I am!
Thanks,
Sean.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#4 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACpoH255cYckdicb3juzdtNDw4EXgRqwks5qyB-IgaJpZM4H0fq2
.

@turbopape
Copy link
Owner Author

Invite sent!

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

No branches or pull requests

2 participants