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.

Sign up for GitHub

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

Jump to bottom

[feature] Implement a Real Interpreter #17

Open
gaocegege opened this issue Sep 10, 2018 · 6 comments
Open

[feature] Implement a Real Interpreter #17

gaocegege opened this issue Sep 10, 2018 · 6 comments
Assignees
@gaocegege
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@gaocegege
Copy link
Contributor

/priority p3
/kind feature

We implement a simple interpreter based on the string comparison, which is not robust. We need to implement a real one.
@caicloud-bot caicloud-bot added priority/P3 kind/feature Categorizes issue or PR as related to a new feature. labels Sep 10, 2018
@gaocegege
Copy link
Contributor Author

/assign

@gaocegege
Copy link
Contributor Author

I want to use goyacc to generate a parser for the interpreter.

@ddysher
Copy link
Member

ddysher commented Sep 13, 2018

we need to first define our language...

@gaocegege
Copy link
Contributor Author

Sure.

@gaocegege gaocegege changed the title [feature] Implement a real interpreter [feature] Implement a Real Interpreter Sep 13, 2018
@caicloud-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@caicloud-bot caicloud-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 12, 2018
@caicloud-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@caicloud-bot caicloud-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 11, 2019
@bbbmj bbbmj removed the priority/P3 label May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaocegege gaocegege

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ddysher @gaocegege @caicloud-bot @bbbmj