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

How can uncaught exception errors be redirected? #210

Open
mrakgr opened this issue Jan 2, 2021 · 0 comments
Open

How can uncaught exception errors be redirected? #210

mrakgr opened this issue Jan 2, 2021 · 0 comments

Comments

@mrakgr
Copy link
Contributor

mrakgr commented Jan 2, 2021

Right now, I suspect Hopac just writes them in the standard error stream of the console, but I'd like to redirect it. I thought of doing my own TextWriter and setting it as the `Console.Error' in order to intercept them that way, but implementing it seems pretty difficult so I thought I should ask around first.

I am doing a language project that is currently in the alpha stage. It was fine to have a console window open while I was working on it alone, but now that Spiral is out on the VS Code marketplace the editor server will be running in the background. Since uncaught exceptions will always be compiler errors, I'd really like to report those as fatal errors in the editor. Besides Hopac which I am using internally for concurrency in the language implementation, at the outermost layer I am using NetMQ to communicate with the editor via TCP. This is why the standard error is not good for me.

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

No branches or pull requests

1 participant