Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

checked exceptions. #213

Open
baroquebobcat opened this Issue Mar 31, 2013 · 6 comments

Comments

Projects
None yet
2 participants
Owner

baroquebobcat commented Mar 31, 2013

the new typer doesn't do them right now.

Contributor

ribrdb commented May 15, 2013

Is this a problem? Scala does not have checked exceptions.
I don't think the bytecode backend has ever implemented checked exceptions.
It was only javac that checked exceptions in the generated .java files.

Owner

baroquebobcat commented May 15, 2013

The problem is that mmeta relies on them, and I had trouble getting it to compile without. I don't have a strong feeling about whether we support them or not, but we did before, so not supporting them was a breaking change.

Contributor

ribrdb commented May 15, 2013

Ah, so you don't need to check them? You just mean supporting the 'throws' macro?

Owner

baroquebobcat commented May 15, 2013

Yeah, is that code somewhere? Maybe I could try to update/fix it.

On Wed, May 15, 2013 at 5:18 PM, ribrdb notifications@github.com wrote:

Ah, so you don't need to check them? You just mean supporting the 'throws'
macro?


Reply to this email directly or view it on GitHubhttps://github.com/mirah/mirah/issues/213#issuecomment-17972303
.

-Nick Howard
http://blog.baroquebobcat.com/

Contributor

ribrdb commented May 15, 2013

I don't think the old code will be useful. This probably needs to work similar to abstract:
* add a new annotation to hold the exceptions
* add an Object.throws macro to add the annotation to the method definition
* update the backends to understand the annotation

Owner

baroquebobcat commented Aug 3, 2013

pushing this off into the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment