blocks|key|2898959|text|我个人更喜欢尽可能模块化地做事情。这样，当你需要在几年后改变一些东西时，你不需要在100个地方改变它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2898960|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|$]]

I personally prefer to do things as modular as possible. That way when you need to change something a few years down the road, you don't have to change it in 100 places.

blocks|key|1209980|text|您应该研究各种框架，这些框架提供了实现更好的代码重用、引导等工具。例如，Symfony、Zend+Framework、Yii等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1209981|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|$]]

You should look into various frameworks that provide tools for implementing better code reuse, bootstrapping, etc. For example, Symfony, Zend Framework, Yii, etc.

blocks|key|1210011|text|如果您使用的是过程代码，则应该根据函数的上下文对函数进行分组。例如：database.php，input.php...|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1210012|如果你正在使用类，你应该只在一个文件中有一个类，并将它包含进来。对于类，您还可以使用spl_autoload_register函数仅在需要时自动加载类。|1210013|如果你有你知道你总是需要的公共代码，你应该创建一个front+controller并且只包含它在那里。|1210014|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/function.spl-autoload-register.php|1|http://en.wikipedia.org/wiki/Front_Controller_pattern^0|Y|C|1B|9|0|16|L|16|L|0|0|P|G|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|J|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

In case you are using procedural code you should group functions by their context. For example into: <code>database.php</code>, <code>input.php</code>...

In case you are using classes you should have one class in only one file and include it. With classes you can also use the <a href="http://php.net/manual/en/function.spl-autoload-register.php" rel="nofollow"><code>spl_autoload_register</code></a> function to autoload classes only when needed.

If you have common code that you know you are always going to need you should create a <a href="http://en.wikipedia.org/wiki/Front_Controller_pattern" rel="nofollow">front controller</a> and include it only there.

blocks|key|1210016|text|当然，您应该将重复的块放在一个文件中，然后将其包含在内。通常是connect.php、functions.php、header.php、menu.php和footer.php|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1210017|entityMap^0|V|B|17|D|1L|A|1W|8|25|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

of course you should put repeating blocks in one file and then include it.
Usually it <code>connect.php</code>, <code>functions.php</code>, <code>header.php</code>, <code>menu.php</code> and <code>footer.php</code>

blocks|key|1210045|text|我相信，编程语言中的命名法为您提供了一个很好的起点来构建代码结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1210046|function+->+does+(only)+1+thing,+and+that+good.
class++++->+collection+of+functions+that+belong+together|code-block|syntax|javascript|1210047|至于"all+in+1+page“部分..您应该只使用让解析器读取它将需要来完成当前任务的代码。如果一个“页面”应该做不止一件事，你应该只在你需要的时候require()你需要的类/函数。|offset|length|style|CODE|1210048|entityMap^0|0|0|24|9|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I believe that the nomenclature in programming languages gives you a good starting point for how to structure your code.

<pre><code>function -&gt; does (only) 1 thing, and that good.
class -&gt; collection of functions that belong together
</code></pre>

as for the "all in 1 page" part.. you should only have the parser read through code that it will need to accomplish its current task. if a single "page" is supposed to do more than 1 thing, you should only <code>require()</code> the classes/functions you need when you need them.

blocks|key|1210079|text|事实上，这并不重要，做你喜欢的事情。在其他答案中给出的原因和很好的例子中，如果你有很多文件，你可能不需要在每个请求中加载所有文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1210080|将所有文件都放在一个文件中可以确保在迁移或分发时，您需要移动或复制单个文件。|1210081|如果我没记错的话，RedBeans只是一个文件，而例如Prado有很多这样的文件。|1210082|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In fact it doesn't matter, do the way you like. Among the reasons and good examples given in other answers, if you have many files, probably you don't need to load all of them on each request.

Having all in one file assures that on migrate or distribute it you need to move or copy a single file.

If I remember correctly RedBeans is just a single file, while for example Prado has lots of them.

I'm going to start making an open source forum and I have the following question:

Should I include all the important code in one php page that i require once on each page or having it on each page.

i.e: A code that connects to the MySQL database, another code that secures the input before executing a query.

PHP: Having all the important code in 1 php page or having it only on pages that require it

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我将开始制作一个开源论坛，我有以下问题：我应该包括所有的重要代码在一个php页面，我需要在每一页或有它在每一页。即:一个连接到MySQL数据库的代码，另一个在执行查询之前保护输入的代码。

问PHP:将所有重要代码放在一个php页面中，或者只在需要它的页面上使用它
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP:将所有重要代码放在一个php页面中，或者只在需要它的页面上使用它EN