Skip to content

Interactivity #329

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

Closed
Tracked by #1600
certik opened this issue Apr 6, 2022 · 3 comments · Fixed by #2617
Closed
Tracked by #1600

Interactivity #329

certik opened this issue Apr 6, 2022 · 3 comments · Fixed by #2617
Assignees

Comments

@certik
Copy link
Contributor

certik commented Apr 6, 2022

Make LPython work in an interactive prompt.

Copy how LFortran does it. We have to remember a symbol table, and compile each prompt as we go. LFortran has all the infrastructure, I think it's not difficult to add to LPython.

@certik certik mentioned this issue Apr 6, 2022
9 tasks
@Thirumalai-Shaktivel Thirumalai-Shaktivel self-assigned this Nov 24, 2022
@certik certik mentioned this issue Mar 21, 2023
38 tasks
@deadtik
Copy link

deadtik commented Mar 31, 2023

Can I get the documentation for LFortran?

@certik
Copy link
Contributor Author

certik commented Apr 1, 2023

@Vipul-Cariappa
Copy link
Contributor

We discussed the following during the last meeting:

Currently, the interactive shell is implemented in LFortran by assigning the parent of a symbol table to the symbol table of the previously executed cell's symbol table. This shadows the previous definition(s). It is advantageous as it allows rewriting symbols. We should try taking a similar approach while implementing the interactive shell for LPython.

Hopefully, we implement the interactive shell such that it can be shared with multiple frontends, i.e. combine LPython and LFortran's implementation. Try using the same implementation with LC frontend.

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

Successfully merging a pull request may close this issue.

4 participants