-
Notifications
You must be signed in to change notification settings - Fork 34
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
Try catch 6.2.0 global persistent exception #49
Closed
gabrielschulhof
wants to merge
7
commits into
nodejs:api-prototype-6.2.0
from
gabrielschulhof:try-catch-6.2.0-global-persistent-exception
Closed
Try catch 6.2.0 global persistent exception #49
gabrielschulhof
wants to merge
7
commits into
nodejs:api-prototype-6.2.0
from
gabrielschulhof:try-catch-6.2.0-global-persistent-exception
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Note: I did not include |
Closed
gabrielschulhof
pushed a commit
to gabrielschulhof/abi-stable-node
that referenced
this pull request
Jan 20, 2017
Re nodejsgh-27 Re nodejsgh-43 (cherry picked from commit 8d8c17fc3458b70abfd2efcaee97538b49ca3008)
gabrielschulhof
force-pushed
the
try-catch-6.2.0-global-persistent-exception
branch
from
January 20, 2017 11:39
5f1c3c3
to
99d28c6
Compare
LGTM. I just had the one minor comment about the latest version. |
Merged
gabrielschulhof
pushed a commit
that referenced
this pull request
Jan 20, 2017
The approach taken is that of JSRT. That is, the last exception arising from calls to NAPI APIs is caught and, if not cleared before control returns to Javascript, it is re-thrown. This creates a "Is exception pending?"/"Retrieve exception and clear exception status!" modus operandi. Closes #49
gabrielschulhof
deleted the
try-catch-6.2.0-global-persistent-exception
branch
January 20, 2017 20:29
jasongin
pushed a commit
to jasongin/abi-stable-node
that referenced
this pull request
Jan 26, 2017
The approach taken is that of JSRT. That is, the last exception arising from calls to NAPI APIs is caught and, if not cleared before control returns to Javascript, it is re-thrown. This creates a "Is exception pending?"/"Retrieve exception and clear exception status!" modus operandi. Closes nodejs#49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementation of JSRT exception semantics in V8.