Closed Rarst closed 8 years ago
I don't think I can't both support composer autoloading and not support it at the same time. If composer doesn't support PHP 5.2, why would you be installing PHP_CodeSniffer using composer under 5.2?
Installing and running are separate actions. We install with Composer, but we support running result on PHP 5.2 version, using a package that generates 5.2–compatible autoload.
So it would make sense for me if including Composer autoload was conditional on PHP >=5.3, because it's presence doesn't guarantee PHP environment that can execute it. People like us who have to support PHP 5.2 :cry: will deal with autoload themselves.
In this specific case we decided to exclude CS check from 5.2 on Travis, version not important to it. So this is just reporting to make it more robust and handle edge case better, not something critical for us.
We install with Composer, but we support running result on PHP 5.2 version, using a package that generates 5.2–compatible autoload.
I didn't know that was possible. Thanks for letting me know.
So it would make sense for me if including Composer autoload was conditional on PHP >=5.3
Sounds like a good idea.
https://github.com/squizlabs/PHP_CodeSniffer/commit/0ade7697cf4a982c08f96957e2fa8a08da140c71 breaks on PHP 5.2 since Composer autoload is not compatible with it.