Ing between common function paths and configuration item paths in ThinkPHP

This article mainly introduces the ing between common function paths and configuration item paths in ThinkPHP. It also analyzes the ing between common function paths and configuration item paths in ThinkPHP and the corresponding modification positions, this helps you better understand the underlying code principles of ThinkPHP. For more information, see the examples in this article to analyze the ing between public function paths and configuration item paths in ThinkPHP. Share it with you for your reference. The specific analysis is as follows:

When using public functions in ThinkPHP (a single entry file corresponds to an independent project), you can write a public function file in the Common folder and write the file name as common. php files are automatically loaded by the system. if they are written as other function names, they are not automatically loaded, but there are two processing mechanisms.

1. manually load the file ('@. function') when using it. in this way, the file will be manually loaded. @ Indicates that it is in the Common folder under this project.

2. configure in the configuration file

The code is as follows:

'Load _ EXT_FILE '=> 'function'

In ThinkPHP, _ PUBLICC _ is not a constant but a ing. it is the Public directory under the root directory by default and can be modified in the configuration file,

The code is as follows:

'Tmpl _ PARSE_STRING '=>. 'public'

I hope this article will help you with ThinkPHP framework programming.