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

no Sub::Uplevel #2

Closed
wants to merge 1 commit into from
Closed

no Sub::Uplevel #2

wants to merge 1 commit into from

Conversation

tobyink
Copy link

@tobyink tobyink commented Apr 16, 2012

This feature restores the built-in caller() function. It needs to be used with care, but can speed up code that uses Sub::Uplevel early on but doesn't need it later.

@dagolden
Copy link

Thanks for taking a cut at writing this. My first reaction is that I think it's brittle. Sub::Uplevel is already something that is pretty crazy and this makes it even crazier. I'd rather see an XS implementation of the "normal" caller override instead to regain the speed when upleveling isn't in effect.

@dagolden
Copy link

As I said, I think trying to reverse a global override is not a great idea. I'm going to close this request.

@dagolden dagolden closed this Mar 27, 2013
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

Successfully merging this pull request may close these issues.

2 participants