Skip to content

Error is not written to error output #109

Description

@jinek

If exception happened while executing gpr it is caught by the catch which just returns code 1

catch (Exception e)

My question is why this catch is needed at all, because runtime aready returns non-zero code by itself, additionally the default handler will write error to error stream and other things, like suggestion to attach the debugger.
Can't we just simply remove it? Does it give any benefits?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions