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

internal exceptions and inline interceptions -- complexities #12

Open
banister opened this issue Oct 2, 2012 · 0 comments
Open

internal exceptions and inline interceptions -- complexities #12

banister opened this issue Oct 2, 2012 · 0 comments

Comments

@banister
Copy link
Member

banister commented Oct 2, 2012

# Internal exceptions (C exceptions) are not intercepted inline (when EE.inline == true) by default.
# This is because a fuck-tonne of internal exceptions are raised (but then rescued) in rubygems, Pry, CodeRay,
# and a bunch of other libraries. In particular, because internal exceptions are raised inside Pry as it begins a session, EE goes into
# an infinite loop as the process of starting a session on an internal exception generates more internal exceptions, which cause another session to start..
# ad infinitum...
# Internal exceptions should only be enabled for inline interception when `EE.intercept` is set to a very selective proc, and is sure to capture only the internal exceptions
# you want, and not the hundreds of other possible internal exceptions that may be raised.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant