blocks|key|1792249|text|你给出了一个反对它的理由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1792250|另一个非常重要的问题是，如果您将编译与运行时分离开来，无论是在每次发生的时间上，还是在运行时的硬件方面，您都会很快遇到复杂的依赖问题--当您尝试在PHP5.3运行时上运行PHP+5.1生成的操作码时，会发生什么？|1792251|它还使代码调试更加困难--因为调试器必须将操作码映射回源代码。|1792252|但是一个非常重要的问题，你似乎没有问过，更不用说回答了，预生成操作码的好处是什么？|1792253|在运行时之前编译操作码比缓存操作码有很大的好处吗？两者之间的差别将微乎其微。|1792254|当然，HipHop的存在理由是，本机编译的PHP代码跑得更快比PHP具有操作码缓存，而牺牲了一些功能。但那是完全不同的。|offset|length|1792255|您认为只有操作码在服务器上才能提高安全性(通过模糊)吗？|1792256|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/facebook/hiphop-php/wiki/|1|http://php.webtutor.pl/en/2011/05/17/drupal-hiphop-for-php-vs-apc-benchmark/^0|0|0|0|0|0|3|6|0|Q|4|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|14|8|@]|9|@$L|15|M|16|1|17]|$L|18|M|19|1|1A]]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

You've given one reason against it.

Another very important one is that if you separate the compile from the runtime both in terms of the time at which each occur but also in terms of the hardware where it runs, you quickly run into complex dependency problems - what happens when you try to run opcode generated by PHP 5.1 on a PHP 5.3 runtime?

It also makes debugging of code harder - since the debugger has to map the opcode back to the source code.

But a very important question you don't seem to have asked let alone answered is what is the benefit of pre-generating the opcode?

Would compiling the opcode prior to runtime have a significant benefit over caching the opcode? The difference would be un-measurably small.

Certainly the raison d'etre for <a href="https://github.com/facebook/hiphop-php/wiki/" rel="nofollow">HipHop</a> is that natively compiled PHP code <a href="http://php.webtutor.pl/en/2011/05/17/drupal-hiphop-for-php-vs-apc-benchmark/" rel="nofollow">runs faster</a> than PHP with opcode caching at the expense of some functionality. But that's something quite different.

Do you think that having only the opcodes on the server improves the security (by obscurity)?

PHP is usually compiled to opcode by the Zend engine on execution time.

To skip the compiling every time one can use an opcode cache like APC to save the opcode in shared memory and reuse it.

Okay, now it seems that there is no solution yet for just compiling the PHP to opcode and using that. Similar to how you use Java.

But why? I am wondering about that b/c this is a quite obvious idea, so I guess there is a reason for this.

EDIT:

the core question is this:

wouldn't make PHP-compilation make opcode-caching superfluous?

The only "reason" against it would be that you couldn't just fix something on the live-system ... which is anyway bad bad bad practice.

Compilation of PHP- to op-code and having the opcode executed

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

PHP通常在执行时由Zend引擎编译成操作码。要跳过编译，每次都可以使用操作码缓存(如APC )将操作码保存在共享内存中并重用它。好的，现在看来还没有解决方案，只需将PHP编译成操作代码并使用它。类似于您如何使用Java。，但是为什么？，我在想b/c --这是一个很明显的想法，所以我想这是有原因的。编辑核心问题是：难道...

编译PHP到op-代码并执行操作码-腾讯云开发者社区-腾讯云

问编译PHP到op-代码并执行操作码
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编译PHP到op-代码并执行操作码EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问编译PHP到op-代码并执行操作码
EN