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

Online Yacc/Lex editor/tester #422

Closed
mingodad opened this issue Sep 20, 2023 · 6 comments
Closed

Online Yacc/Lex editor/tester #422

mingodad opened this issue Sep 20, 2023 · 6 comments

Comments

@mingodad
Copy link

Would be nice if this project could also have something like https://mingodad.github.io/parsertl-playground/playground/ (repository here https://github.com/mingodad/parsertl-playground) to allow edit/debug/test Yacc/Lex grammars online.

Any feed back is welcome !

@ltratt
Copy link
Member

ltratt commented Sep 20, 2023

If someone wanted to create such a thing, we'd happily link to it, but I doubt I'll find the time myself I'm afraid.

@mingodad
Copy link
Author

Have you already looked at it ?

@mingodad
Copy link
Author

Also there is several non trivial grammars there that can be used by this project !

@ltratt
Copy link
Member

ltratt commented Sep 20, 2023

It looks cool. Like I said, it'll take someone other than me to do this I'm afraid.

@ratmice
Copy link
Collaborator

ratmice commented Sep 21, 2023

Like I said in #385, I have always been planning on porting nimbleparse_lsp to wasm, and making a playground version available.
I have at least made various attempts locally but nothing has panned out. If anyone has more rust-wasm and editor-wasm interface familiarity or just wants to help in that regard I would be very grateful, the specific issue for that work is ratmice/nimbleparse_lsp#6 (I should probably leave what I have tried/gotten stuck on in that linked issue). It may be worthwhile looking at other web based editors than vscode which support LSP and see if any others are easier to undertake an initial port on. I haven't actually seen any vscode web-extensions running rust compiled wasm code, so (afaik) there is little in the way of prior art to reference on that undertaking.

Anyhow that is still my plan/focus regarding this issue.

@ltratt
Copy link
Member

ltratt commented Sep 21, 2023

Thanks @ratmice!

@ltratt ltratt closed this as completed Sep 21, 2023
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

3 participants