-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
removed Mage_Compiler #534
removed Mage_Compiler #534
Conversation
Does it make sense to fix the autoloader at the same time? It should be returning a false if the class isn't found. That would allow people to easily use composer autoloader in conjunction. |
Will look over this later and implement it.
Am Freitag, 21. September 2018 schrieb Lee Saferite :
… Does it make sense to fix the autoloader at the same time?
It should be returning a false if the class isn't found. That would allow
people to easily use composer autoloader in conjunction.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#534 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAzB7_PHVxk-P8fpQ2yRjR2GELiWmJruks5udQxTgaJpZM4W0JmY>
.
|
c508ac9
to
140259e
Compare
@seansan as mentioned i added the missing return statement for the autoloader. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should Varien_Autoload::registerScope method be kept (doesn't need to do anything) just for BC?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also any reason not to go ahead and replace __autoload
with spl_autoload_register
since the former is deprecated in PHP 7.2?
the __autoload function can get deleted completely. Since the Varien Autoloader uses the SPL autoloader, this one is never in use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the BC break is I think acceptable.
usage is very low (or hard to find via github) and it fails early, so its fast to notice and easy to fix.
also, when keeping we would maybe also need to keep the other scope related functions...
I suggest to wait in this case, if there is really someone who is using this extensively.
Fixing the autoload function is easy done over a separate PR then afterwards
8507700
Removed Mage_Compiler #525