You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
robocoder opened this issue
May 11, 2010
· 0 comments
Labels
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
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)
The text was updated successfully, but these errors were encountered:
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
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:
Cons:
The text was updated successfully, but these errors were encountered: