blocks|key|4593085|text|使用自动加载器总是有好处的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4593086|4593087|您不需要在每个文件的顶部包含大量的include+|unordered-list-item|4593088|您不必担心忘记include|4593089|自动加载器只包含必要的文件，并且当它们需要时|4593090|4593091|潜在的缺点|4593092|4593093|在aotoloader和您想要的库使用的自动加载器之间发生冲突|4593094|4593095|通过向spl注册自动加载器可以避免潜在的缺陷|4593096|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|12|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|14|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|T|$]]

<p>Using an autoloader is always advantageous.</p>

<ul>
<li>You don't need massive collections of includes at the top of every
file </li>
<li>You don't have to worry about forgetting an include </li>
<li>Autoloader
only includes files that are necessary, and as they are needed</li>
</ul>

<p>Potential drawbacks</p>

<ul>
<li>Clash between your aotoloader and autoloaders used by libraries you want</li>
</ul>

<p>Potential drawback can be avoided by registering your autoloader with spl</p>


blocks|key|4593123|text|马克说的话。此外，如果这对你很重要，你可以保持你的代码干燥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4593124|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

<p>What Mark said. Also, you can keep your code DRY, if that's important to you.</p>


blocks|key|4593157|text|自动加载文件的好处是您不需要担心自己加载文件。并且这些文件只在需要时才会加载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4593158|一个更好的自动加载函数是更新的：http://php.net/manual/en/function.spl-autoload-register.php|offset|length|4593159|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/function.spl-autoload-register.php^0|0|G|1N|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

<p>The advantage if autoloading files is you don't need to worry about loadng the files yourself. And the files only gets loaded when they are needed.</p>

<p>An even better autoload function would be the newer: <a href="http://php.net/manual/en/function.spl-autoload-register.php" rel="nofollow">http://php.net/manual/en/function.spl-autoload-register.php</a></p>


blocks|key|1526107|text|我不相信__autoload只有优点。但确实有一些。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1526108|__autoload的优点|1526109|1526110|你不需要维护那么长的include列表，这可能是保持整洁的痛苦(这意味着不会忘记include)|unordered-list-item|1526111|你只需要包括你真正需要的:一些类可能只在一些特殊的场景中需要，你可以避免它|1526112|1526113|正常方式的优点|1526114|对于anybody|1526115|Looking来说，在includes中很容易理解，includes会告诉你文件正在做什么，你可以控制你正在导入的类的列表(如果你不想要一个类，因为它太大或者不能工作，它永远不会被包含在内)|1526116|
|1526117|+__autoload函数没有任何复杂性。如果您的类位于复杂的层次结构中，则只需键入名称，而无需编写复杂的代码即可找到正确的文件。|1526118|1526119|更易于调试:可能令人担忧的代码的范围仅限于您做过的includes。|1526120|1526121|这实际上是一个编码风格的问题。|1526122|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|16|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|G|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|G|7|1C|8|@]|9|@]|A|$]]|$1|U|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|V|3|W|5|G|7|1E|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1G|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|11|$]]

<p>I don't believe __autoload only has advantages. But there are some indeed.</p>

<h2>Pros for __autoload</h2>

<ul>
<li>You don't need to maintain that long list of includes, which can be a pain to keep up tidy (which means there's no forgetting an include)</li>
<li>You only include what you really need: some classes might only be needed in some special scenario, you can avoid it</li>
</ul>

<h2>Pros for the normal way</h2>

<ul>
<li>It's very easy to understand for anybody</li>
<li>Looking at the includes will tell you what kind of things the file is doing</li>
<li>You control the list of classes you're importing (if you don't want a class because it's huge or doesn't work, it will never get included) </li>
<li>There's no complexity in the __autoload function. If your classes are in a complex hierarchy, you just need to type the name, and don't need to write complex code to find the correct file.</li>
<li>Easier to debug: the scope of the code that could be worrying is limited to the includes you did.</li>
</ul>

<p>It's really a matter of coding style.</p>


blocks|key|4593274|text|我想我最同意Cygal的观点，但我想修改一下回应，将PSR-0考虑在内。如果你不遵守这个标准，我认为使用自动加载没有多大意义。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4593275|Pro自动加载|4593276|4593277|无需维护包含列表。|unordered-list-item|4593278|您只包含您真正需要的内容。|4593279|代码保持可读性。|4593280|您遵循所有主要|4593281|框架采用的标准，因此您可以期待人们熟悉这种方法。|4593282|支持旧风格|4593283|4593284|依赖关系很容易在代码文件的头中看到。|4593285|在类名和文件路径之间没有必要的映射。如果您经常使用自动加载，则可能有必要减少使用缓存重复计算此映射所浪费的时间。|4593286|4593287|总而言之:只要你遵循PSR-0，我就看不到任何避免自动加载的理由！|style|BOLD|4593288|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md^0|Q|5|0|0|0|0|0|0|0|0|0|0|0|0|0|0|T|4|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|D|3|E|5|6|7|1F|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|1H|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|1I|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|1J|8|@]|9|@]|C|$]]|$1|N|3|O|5|I|7|1K|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1L|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1M|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|U|3|V|5|I|7|1O|8|@]|9|@]|C|$]]|$1|W|3|X|5|I|7|1P|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|1R|8|@$A|1S|B|1T|11|12]]|9|@]|C|$]]|$1|13|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]]|14|$15|$5|16|17|18|C|$19|1A]]]]

<p>I think I would agree most with Cygal but would like to amend the response taking <a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md" rel="nofollow">PSR-0</a> into account. I don't think it makes much sense using autoloading if you don't adhere to that standard.</p>

<h1>Pro Autoloading</h1>

<ul>
<li>No need to maintain the include list.</li>
<li>You only include what you really need.</li>
<li>Code remains readable.</li>
<li>You follow a standard adopted by all major PHP frameworks so you can expect that people are familiar with this approach.</li>
</ul>

<h1>Pro old style</h1>

<ul>
<li>The dependencies are easily visible in the header of the code files.</li>
<li>There is no mapping between class names and file paths necessery. If you use autoloading a lot it might be necessary to reduce the time wasted for repeatedly calculating this mapping by using a cache.</li>
</ul>

<p>To summarize: I don't see any reason to avoid autoloading <strong>as long as you follow PSR-0</strong>!</p>


<p>I have been trying to learn about classes in PHP and part of my learning process has been looking at various libraries and stuff out there. Of course I am left with many questions, here is one of them.</p>

<p>When looking at some libraries, the main file that you call to invoke the library, they call each of the libraries files by invoking them directly by name, for example this is how the  PHP chart library does it:</p>

<pre><code>&lt;?php
require_once 'model/ChartConfig.php';
require_once 'model/Point.php';
require_once 'model/DataSet.php';
require_once 'model/XYDataSet.php';
require_once 'model/XYSeriesDataSet.php';

require_once 'view/primitive/Padding.php';
require_once 'view/primitive/Rectangle.php';
require_once 'view/primitive/Primitive.php';
require_once 'view/text/Text.php';
require_once 'view/color/Color.php';
require_once 'view/color/ColorSet.php';
require_once 'view/color/Palette.php';
require_once 'view/axis/Bound.php';
require_once 'view/axis/Axis.php';
require_once 'view/plot/Plot.php';
require_once 'view/caption/Caption.php';
require_once 'view/chart/Chart.php';
require_once 'view/chart/BarChart.php';
require_once 'view/chart/VerticalBarChart.php';
require_once 'view/chart/HorizontalBarChart.php';
require_once 'view/chart/LineChart.php';
require_once 'view/chart/PieChart.php';
?&gt;
</code></pre>

<p>However, I look at another library, and they just automate the process by calling each file in the directory using the PHP autoload method like this(From the php manual):</p>

<pre><code>function __autoload($name) {
    echo "Want to load $name.\n";
    throw new Exception("Unable to load $name.");
}
</code></pre>

<p>I was just wondering if there is any advantage or disadvantage to doing it the autoload way? </p>


Including class files PHP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我一直在尝试学习PHP中的类，我的学习过程的一部分是查看各种库和其他东西。当然，我还有很多问题要问，这里就是其中之一。当查看一些库时，您调用来调用库的主文件，它们通过直接调用名称来调用每个库文件，例如，PHP图表库就是这样做的：<?phprequire_once 'model/ChartConfig.php';requ...

问包括类文件PHP
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问包括类文件PHPEN