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

[Feature] Add option --stringCode to commands compile, run and analyse to allow the use of code as a cmd argument #100

Closed
2 tasks done
Tracked by #112 ...
Luna-Klatzer opened this issue May 17, 2022 · 1 comment · Fixed by #112
Closed
2 tasks done
Tracked by #112 ...
Assignees
Labels
feature New feature or enhancement

Comments

@Luna-Klatzer
Copy link
Member

Luna-Klatzer commented May 17, 2022

Is there an existing proposal for this?

  • I have searched the existing issues

This feature does not exist in the latest version

  • I am using the latest version

Proposal

Implement the support for the -s cmd argument that allows a string to be passed to the Kipper compiler.

Exact behaviour you want

Implement the -s option to the Kipper commands compile, run and analyse and allow the analysis/compilation/execution of strings.

For example:

kipper run --stringCode="call print(\"Hello world!\");"

This command should execute the string as if it were a file using the default anonymous-script file identifier.

@Luna-Klatzer Luna-Klatzer added the feature New feature or enhancement label May 17, 2022
@Luna-Klatzer Luna-Klatzer self-assigned this May 17, 2022
@Luna-Klatzer Luna-Klatzer pinned this issue May 17, 2022
@Luna-Klatzer Luna-Klatzer changed the title [Feature] Add option -s to commands compile, run and analyse to allow the use of code as a cmd argument [Feature] Add option --stringCode to commands compile, run and analyse to allow the use of code as a cmd argument May 20, 2022
@Luna-Klatzer
Copy link
Member Author

Implemented with #112

Repository owner moved this from Todo to Done in Kipper Language Development May 20, 2022
@Luna-Klatzer Luna-Klatzer unpinned this issue May 20, 2022
This was referenced May 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment