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

Post-refactoring: Handling undefined methods #1349

Closed
robocoder opened this issue May 11, 2010 · 0 comments
Closed

Post-refactoring: Handling undefined methods #1349

robocoder opened this issue May 11, 2010 · 0 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@robocoder
Copy link
Contributor

The runkit PECL extension provides a reload method; the orphaned classkit extension has an experimental addMethod.

In lieu, can we use !__call and !__callStatic methods to handle the case where a class file is overwritten but the old copy is already loaded in memory, and a call is made to a new method?

Pros:

  • doesn't require optional extensions

Cons:

  • would have to be present in all (foreseeable) classes
  • small bang (benefit); big buck (effort)
@robocoder robocoder added this to the Future releases milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

1 participant