blocks|key|51298|text|有不止一个理由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|51299|做|51300|error_reporting(E_ALL);|code-block|syntax|javascript|51301|在您的脚本开始时，您将立即看到所有的原因。|51302|撇开乐趣，在实践中你可能会认为，这是我可能会逃脱的事情。你可能是对的。但作为一名开发人员，你必须在什么是可接受的黑客攻击以及什么是口头辱骂的理由上划出界限。对我来说，这种特殊的行为超出了这一界限。|51303|的最直接的原因是它使error_reporting(E_ALL)不可用。良好的开发实践要求报告所有错误，这些通知为您设置了错误代码和更困难的调试会话。|offset|length|style|CODE|51304|更新：--我没有解决现有情况的实际解决方案的问题，下面是我将在您的位置上所做的工作：|BOLD|51305|51306|找到了责任人，并确保他们再也不会以任何必要的方式再次这样做。|ordered-list-item|51307|运行一个有问题的脚本，并从日志文件中获得关于未定义常量的所有通知。使用regex搜索和替换的|51308|，尝试将\[(a-zA-Z_-)\]替换为['$1']+(或类似的东西)。如果替换的数量等于日志文件中的通知数量，则为黄金。否则，试着分而治之，直到您看到正则表达式是failing.|51309|Repeat为止，这是所有其他脚本所需要的。|51310|51311|entityMap^0|0|0|0|0|0|A|M|0|0|3|0|0|0|0|4|E|L|6|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1B|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@$O|1E|P|1F|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1G|8|@$O|1H|P|1I|Q|U]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|1K|8|@]|9|@]|A|$]]|$1|Z|3|10|5|Y|7|1L|8|@]|9|@]|A|$]]|$1|11|3|12|5|Y|7|1M|8|@$O|1N|P|1O|Q|R]|$O|1P|P|1Q|Q|R]]|9|@]|A|$]]|$1|13|3|14|5|Y|7|1R|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|17|$]]

There is more than one good reason.

Do

<pre><code>error_reporting(E_ALL);
</code></pre>

in the beginning of your script and you will see all the reasons at once.

Fun aside, in practice you might think that well, this is something that I might get away with. And you could be right. But as a developer you have to draw the line somewhere about what is an acceptable hack and what is reason for verbal abuse. For me, this particular behavior is beyond that line.

The very immediate reason why this is bad is that it makes <code>error_reporting(E_ALL)</code> unusable. And good development practice demands that all errors are reported, these notices are setting you up for buggier code and harder debugging sessions.

Update: I didn't address the issue of a practical solution to the existing situation, so here's what I would do in your shoes:

<ol>
<li>Find the person responsible and make sure that they never, ever do this again by any means necessary.</li>
<li>Run a problematic script and get all the notices about undefined constants from the log file.</li>
<li>Using regex search and replace from your editor, try to replace <code>\[(a-zA-Z_-)\]</code> to <code>['$1']</code> (or something similar). If the number of replacements is equal to the number of notices in the log file, you are golden. Otherwise, try divide and conquer until you see where the regex is failing.</li>
<li>Repeat as required for all the other scripts.</li>
</ol>

blocks|key|50349|text|从技术上讲，这样做是不对的。你应该用单引号。如果您修复这些代码，它将使用较少的cpu周期和内存来运行代码。即使在一个文件中有1000个固定的，您会注意到差异吗？可能不会。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50350|如果您修复它，它将是正确的，没有警告或通知，而不是真正的速度或内存使用。|50351|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's not technically correct to do it that way. You should probably use single quotes. It will use less cpu cycles and memory to run the code if you fix those. Will you notice a difference even if there are 1000 of those fixed in one file? Probably not. 

If you fix it, it would be for correctness and not having warnings or notices, not really for speed or memory usage.

blocks|key|1116834|text|我要加上引号。如果没有其他的话，以确保：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1116835|1116836|代码可读性不会降低(如果有人认为您使用的是常量而不是字符串值)，|ordered-list-item|1116837|额外的循环不会浪费在每个评估|1116838|上|1116839|话虽如此，我知道程序员的时间是宝贵的。因此，您可以选择懒散的编码器，并使用正则表达式，如下所示：|1116840|$input+=+'$row_rsCatalogsItems[Name]';
$str+=+preg_replace('/(\$[a-zA-Z_]%2B\[)([a-zA-Z]%2B)(\])/',+'${1}\'${2}\'${3}',+$input);
echo+$str;|code-block|syntax|javascript|1116841|(您可能需要使用该表达式来逐步完成这些更改，以确保您正在更改正确的内容；)|1116842|entityMap^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|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|10|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I'd add the quotes. If nothing else, to ensure that:

<ol>
<li>Code readability isn't reduced (which it is if someone thinks you're using some constant rather than a string value)</li>
<li>Extra cycles aren't wasted on each evaluation</li>
</ol>

Having said that, I understand that a programmer's time is valuable. Therefore, you can optionally out-lazy the lazy coder and use a regular expression like the following:

<pre><code>$input = '$row_rsCatalogsItems[Name]';
$str = preg_replace('/(\$[a-zA-Z_]+\[)([a-zA-Z]+)(\])/', '${1}\'${2}\'${3}', $input);
echo $str;
</code></pre>

(You might want to step through the changes using that expression just to make sure you're changing the right things ;))

I'm running through someone else's code, and they constantly avoid escaping their array keys. 

For example:

$row_rsCatalogsItems[Name]

instead of

$row_rsCatalogsItems['Name']

so I'm constantly making tiny changes to everything I touch just to deal with that bit of laziness. But now I'm wondering whether there's even much benefit to doing so. I get that it'll check for constants before defaulting to a string (I detest that behavior in php when dealing with constants, since they validate to true even if not defined), but I'm not sure even that is worth the bother of changing all the many, many instances of constants-as-array-keys.

Suggestions?

php: Are there great reasons to quote all array keys/indexes?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正在运行其他人的代码，他们经常避免转义数组键。例如：$row_rsCatalogsItemsName而不是$row_rsCatalogsItems‘’Name‘所以我不断地对我所接触的每一件事都做一些微小的改变，仅仅是为了对付那种懒惰。但现在我想知道这样做是否有多大的好处。我得到的结果是，在默认使用字符串之前，它会检...

问php:有很好的理由引用所有数组键/索引吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问php:有很好的理由引用所有数组键/索引吗？EN