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

CLI doesn't properly deal with errors #97

Closed
dahlia opened this issue Mar 1, 2017 · 2 comments
Closed

CLI doesn't properly deal with errors #97

dahlia opened this issue Mar 1, 2017 · 2 comments
Assignees
Labels
cmp:frontend Component: Compiler frontend (e.g., CLI, parser, AST) dfct:easy Difficulty: Easy typ:bug Type: Bug/defect

Comments

@dahlia
Copy link
Member

dahlia commented Mar 1, 2017

The current nirum CLI terminates with exit code 0 even when it's errored. Also it prints error messages into stdout instead of stderr.

We could utilize die function provided by the standard library System.Exit module.

@dahlia dahlia added typ:bug Type: Bug/defect dfct:easy Difficulty: Easy labels Mar 1, 2017
@dahlia
Copy link
Member Author

dahlia commented Mar 7, 2017

@admire93 @AiOO See also Exit Codes With Special Meanings.

@kanghyojun kanghyojun moved this from Chosen to In review in Sprint at Jeju in March 2017 Mar 10, 2017
@kanghyojun
Copy link
Member

Fixed #108

@AiOO AiOO moved this from In review to Delivered in Sprint at Jeju in March 2017 Mar 11, 2017
@dahlia dahlia added the cmp:frontend Component: Compiler frontend (e.g., CLI, parser, AST) label Aug 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmp:frontend Component: Compiler frontend (e.g., CLI, parser, AST) dfct:easy Difficulty: Easy typ:bug Type: Bug/defect
Projects
No open projects
Development

No branches or pull requests

3 participants