I have seen many open-source projects as class. class name. php. class. php: where is the position of this class suitable? I personally respect it. class. php format, because in this way, after a third-party class library is imported to a specified class library in some frameworks... I have seen many open-source projects as class. class name. php. class. php: where is the position of this class suitable?
I personally admire the form of. class. php, because in this way, you can import a third-party class library in some frameworks and specify the class library suffix as. class. php.
Reply content:
I have seen many open-source projects as class. class name. php. class. php: where is the position of this class suitable?
I personally admire the form of. class. php, because in this way, you can import a third-party class library in some frameworks and specify the class library suffix as. class. php.
*. Config. php
*. Function. php
*. Class. php
The above is suitable for small code use, and everything is lost in a directory.
If not, such a file name is not required.
Recommended to understand the php psr-4: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4-autoloader.md
This is a habit problem, or followPSR-4
After all, there arecomposer
Automatically generates mappings between namespaces and source files.
I personally think that if it is a php file
That's the end of php.
No need to differentiate the class file configuration file function files
For more information, see the items on the top of http://packagist.org/
It should end with php!