Context Navigation

Changes between Initial Version and Version 1 of Ticket #36335, comment 16

initial	v1
1	1	I did not want to delve too deep into the dependency/package management topic, as I find that this is a completely separate problem to solve from autoloading. Having Composer provide both adds to the general confusion, as they often get thrown into the same bucket.
2	2
3		However, what @greg1anderson says is completely true. When you try to load two conflicting libraries, you will always have an issue, no matter how many autoloaders you throw in-between. They will only obfuscate the real issue, and the sooner you get an error message about the conflict, the better. PHP can ever know about 1 version of a given class, whether that was `include`d or autoloaded...
	3	However, what @greg1anderson says is completely true. When you try to load two conflicting libraries, you will always have an issue, no matter how many autoloaders you throw in-between. They will only obfuscate the real issue, and the sooner you get an error message about the conflict, the better. PHP can only ever know about 1 version of a given class, whether that was `include`d or autoloaded...
4	4
5	5	However, I want to clarify one technical nuance from the comment above: