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.

Sign up for GitHub

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

Jump to bottom

Error handling during import/export #13

Open
GoogleCodeExporter opened this issue Feb 14, 2016 · 1 comment
Open

Error handling during import/export #13

GoogleCodeExporter opened this issue Feb 14, 2016 · 1 comment
Labels
auto-migrated Priority-Low Type-Other

Comments

@GoogleCodeExporter
Copy link 

The interfaces KeyValueImport and KeyValueExport do not allow their convert
() method to throw an exception. I think that it is crucial that these 
methods can report conversion errors back to Jaql (w/o using runtime 
exceptions), either using declared exceptions or a return value.

Original issue reported on code.google.com by [email protected] on 24 Mar 2009 at 10:58
@GoogleCodeExporter
Copy link
Author 

Exception handling needs an overhaul in general. This is one of the items that 
will 
be addressed.

Original comment by [email protected] on 25 Mar 2009 at 5:54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Low Type-Other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter