blocks|key|3123937|text|PHP2021更新：从+8开始，这两个字符不相同。序列#[是used+for+Attributes。(感谢i336的评论)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3123938|原始答案：|3123939|这个问题的答案是，在中使用"#“和"//”表示单行注释有什么不同吗？？is+no.|3123940|这是没有区别的。通过查看PHP源代码的解析部分，both+"#"+and+"//"+are+handled+by+the+same+code和因此具有完全相同的行为。|3123941|entityMap|0|LINK|mutability|MUTABLE|url|https://stitcher.io/blog/attributes-in-php-8|1|https://stackoverflow.com/questions/9093609/can-i-use-a-hash-sign-for-commenting-in-php/9093787?noredirect=1#comment115854883_9093787|2|https://github.com/php/php-src/blob/ea1ea33bd5d967e9c04046c1af869e4e8b53116e/Zend/zend_language_scanner.l#L2050^0|B|1E|R|2|U|J|0|1H|4|1|0|0|5|0|0|15|0|0|2B|O|1A|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|D]]|E|@$9|13|A|14|1|15]|$9|16|A|17|1|18]]|F|$]]|$1|G|3|H|5|6|7|19|8|@$9|1A|A|1B|B|C]]|E|@]|F|$]]|$1|I|3|J|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|E|@]|F|$]]|$1|K|3|L|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|E|@$9|1I|A|1J|1|1K]]|F|$]]|$1|M|3|-4|5|6|7|1L|8|@]|E|@]|F|$]]]|N|$O|$5|P|Q|R|F|$S|T]]|U|$5|P|Q|R|F|$S|V]]|W|$5|P|Q|R|F|$S|X]]]]

2021 UPDATE: As of PHP 8, the two characters are not the same. The sequence <code>#[</code> is <a href="https://stitcher.io/blog/attributes-in-php-8" rel="noreferrer">used for Attributes</a>.(Thanks to <a href="https://stackoverflow.com/questions/9093609/can-i-use-a-hash-sign-for-commenting-in-php/9093787?noredirect=1#comment115854883_9093787">i336</a> for the comment)
Original Answer:
The answer to the question Is there any difference between using &quot;#&quot; and &quot;//&quot; for single-line comments in PHP? is no.
There is no difference. By looking at the parsing part of PHP source code, <a href="https://github.com/php/php-src/blob/ea1ea33bd5d967e9c04046c1af869e4e8b53116e/Zend/zend_language_scanner.l#L2050" rel="noreferrer">both &quot;#&quot; and &quot;//&quot; are handled by the same code</a> and therefore have the exact same behavior.

blocks|key|242997|text|PHP的文档描述了注释的不同可能性。请参阅http://www.php.net/manual/en/language.basic-syntax.comments.php|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|242998|但是它没有提到"//“和"#”之间的任何区别。所以不应该有技术上的差异。PHP使用C语法，所以我认为这就是为什么大多数程序员使用C风格的注释'//‘的原因。|242999|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/manual/en/language.basic-syntax.comments.php^0|L|1R|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

PHP's documentation describes the different possibilities of comments. See <a href="http://www.php.net/manual/en/language.basic-syntax.comments.php" rel="noreferrer">http://www.php.net/manual/en/language.basic-syntax.comments.php</a>

But it does not say anything about differences between "//" and "#". So there should not be a technical difference. PHP uses C syntax, so I think that is the reason why most of the programmers are using the C-style comments '//'.

blocks|key|2909548|text|<?php
++++echo+'This+is+a+test';+//+This+is+a+one-line+C%2B%2B+style+comment
++++/*+This+is+a+multi-line+comment.
+++++++Yet+another+line+of+comment.+*/
++++echo+'This+is+yet+another+test.';
++++echo+'One+Final+Test';+#+This+is+a+one-line+shell-style+comment
?>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2909549|RTM|unstyled|offset|length|2909550|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/language.basic-syntax.comments.php^0|0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>&lt;?php
 echo 'This is a test'; // This is a one-line C++ style comment
 /* This is a multi-line comment.
 Yet another line of comment. */
 echo 'This is yet another test.';
 echo 'One Final Test'; # This is a one-line shell-style comment
?&gt;
</code></pre>

<a href="http://php.net/manual/en/language.basic-syntax.comments.php" rel="noreferrer">RTM</a>

blocks|key|2909729|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2909730|除了个人喜好之外，还有什么原因让评论使用//而不是#吗？|blockquote|2909731|2909732|2909733|我认为这只是个人喜好。//和#之间没有区别。我个人使用#表示一行注释，//表示注释代码，/**++*/表示块注释。|offset|length|style|CODE|2909734|<?php
++++#+This+is+a+one-line+comment
++++echo+'This+is+a+test';

++++//+echo+'This+is+yet+another+test';+//+commenting+code

++++/**+
+++++*+This+is+a+block+comment
+++++*+with+multi-lines+
+++++*/
++++echo+'One+final+test';
?>|code-block|syntax|javascript|2909735|entityMap^0|0|0|0|0|B|2|E|1|R|1|Z|2|18|7|0|0^^$0|@$1|2|3|-4|4|5|6|S|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|T|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|U|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|W|7|@$H|X|I|Y|J|K]|$H|Z|I|10|J|K]|$H|11|I|12|J|K]|$H|13|I|14|J|K]|$H|15|I|16|J|K]]|8|@]|9|$]]|$1|L|3|M|4|N|6|17|7|@]|8|@]|9|$O|P]]|$1|Q|3|-4|4|5|6|18|7|@]|8|@]|9|$]]]|R|$]]

<blockquote>
 Is there any reason, aside from personal preference, to use // rather than # for comments?
</blockquote>

I think it is just a personal preference only. There is no difference between <code>//</code> and <code>#</code>. I personally use <code>#</code> for one-line comment, <code>//</code> for commenting out code and <code>/** */</code> for block comment.

<pre><code>&lt;?php
 # This is a one-line comment
 echo 'This is a test';

 // echo 'This is yet another test'; // commenting code

 /** 
 * This is a block comment
 * with multi-lines 
 */
 echo 'One final test';
?&gt;
</code></pre>

blocks|key|237929|text|有人可能认为#形式的注释主要是为了使用熟悉的"shebang“(#!)创建shell脚本。符号。在下面的脚本中，PHP应该忽略第一行，因为它也是一个注释。示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|237930|#!/usr/bin/php
<?php

echo+"Hello+PHP\n";|code-block|syntax|javascript|237931|如果您将其存储在可执行文件中，则可以从终端运行它，如下所示|237932|./hello|237933|输出为|237934|Hello+PHP|237935|然而，这种推理是不正确的，如下面的反例所示：|237936|#!/usr/bin/php
#A
<?php

#B
echo+"Hello+PHP\n";|237937|解释器特别忽略了第一行(+shebang行)。PHP标记前的注释行被回显到标准输出，因为它不在PHP标记内。开始PHP标记之后的注释被解释为PHP代码，但它被忽略，因为它是一个注释。|237938|修订版的输出为|237939|#A
Hello+PHP|237940|entityMap^0|6|1|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|18|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1A|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1C|8|@]|D|@]|E|$]]|$1|U|3|V|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|W|3|X|5|6|7|1E|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|D|@]|E|$]]|$1|10|3|11|5|H|7|1G|8|@]|D|@]|E|$I|J]]|$1|12|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|13|$]]

One might think that the <code>#</code> form of commenting is primarily intended to make a shell script using the familiar "shebang" (#!) notation. In the following script, PHP should ignore the first line because it is also a comment. Example:

<pre><code>#!/usr/bin/php
&lt;?php

echo "Hello PHP\n";
</code></pre>

If you store it in an executable file you can then run it from a terminal like this

<pre><code>./hello
</code></pre>

The output is 

<pre><code>Hello PHP
</code></pre>

However, this reasoning is incorrect, as the following counterexample shows:

<pre><code>#!/usr/bin/php
#A
&lt;?php

#B
echo "Hello PHP\n";
</code></pre>

The first line (the shebang line) is specially ignored by the interpreter. The comment line before the PHP tag is echoed to standard output because it is not inside a PHP tag. The comment after the opening PHP tag is interpreted as PHP code but it is ignored because it is a comment.

The output of the revised version is

<pre><code>#A
Hello PHP
</code></pre>

blocks|key|240435|text|如果您在团队/项目中建立了一些规则集...这两种类型的注释可以用来概述注释代码的目的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|240436|例如，我喜欢使用#来静音/禁用配置设置、子函数，以及通常是有用或重要的代码，但目前只是禁用。|offset|length|style|CODE|240437|entityMap^0|0|8|1|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you establish some rule sets in your team / project... the 2 types of comments can be used to outline the purpose of the commented code.

For example I like to use <code>#</code> to mute / disable config settings, sub functions and in general a piece of code that is useful or important, but is just currently disabled.

blocks|key|243088|text|没有关于这方面的官方PSR。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|243089|但是，在所有PSR示例代码中，它们都使用//作为内联注释。|offset|length|style|CODE|243090|有一个PSR-2扩展提案旨在标准化它，但它不是官方的：https://github.com/php-fig-rectified/fig-rectified-standards/blob/master/PSR-2-R-coding-style-guide-additions.md#commenting-code|243091|在PHP文化中更常用的是//，但是也可以使用#。我个人喜欢它，因为它更短，节省了字节。这是个人喜好和偏见，没有正确的答案，直到，当然，它成为一种标准，这是我们应该尽量遵循的东西。|243092|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/php-fig-rectified/fig-rectified-standards/blob/master/PSR-2-R-coding-style-guide-additions.md#commenting-code^0|0|K|2|0|R|3K|0|0|C|2|M|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|K|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

<h3>There's no official PSR for that.</h3>
However, in all PSR example code, they use <code>//</code> for inline comments.
There's an PSR-2 extension proposal that aims to standardize it, but it's not official: <a href="https://github.com/php-fig-rectified/fig-rectified-standards/blob/master/PSR-2-R-coding-style-guide-additions.md#commenting-code" rel="nofollow noreferrer">https://github.com/php-fig-rectified/fig-rectified-standards/blob/master/PSR-2-R-coding-style-guide-additions.md#commenting-code</a>
<code>//</code> is more commonly used in the PHP culture, but it's fine to use <code>#</code> too. I personally like it, for being shorter and saving bytes. It's personal taste and biased, there's no right answer for it, until, of course, it becomes a standard, which is something we should try to follow as much as possible.

blocks|key|241512|text|是的，但是存在跨平台的差异。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|241513|我一直在PHP中使用#进行注释，但我注意到了采用情况的不同。|241514|在windows键盘上，#键很容易使用。在mac键盘上，#键基本上不存在。|241515|因此对于mac用户来说，Alt+%2B3或⌥%2B3比//更难输入，所以//已经成为一种显示带有注释的代码的跨平台方式。|241516|这是我的观察。|241517|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Yes, however there are cross platform differences.

I use # all the time for commenting in PHP, but I have noticed an adoption difference.

On windows keyboard the # key is easy to use.
On mac keyboard # key mostly isn't present.

So for mac users, [Alt] + [3] or [⌥] + [3] is more difficult to type than //, so // has become a cross platform way of displaying code with comments.

This is my observation.

blocks|key|2909914|text|来自https://php.net/manual/en/migration53.deprecated.php|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2909915|“在.INI文件中，以'#‘开头的PHP5.3.x+...Comments中不推荐使用的功能现已弃用。”|2909916|这就对了。默认情况下，散列“#”显示为注释选项，不推荐使用。我计划使用它来区分嵌套的if/else语句的不同层，并标记它们的结束括号，或者像其他人在相关帖子中建议的那样，使用它来区分代码注释和注释掉的代码。(注意:+Link在19年4月23日是有效的，尽管当您阅读本文时，谁知道它是否还能工作呢？)|2909917|entityMap|0|LINK|mutability|MUTABLE|url|https://php.net/manual/en/migration53.deprecated.php^0|2|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

From <a href="https://php.net/manual/en/migration53.deprecated.php" rel="nofollow noreferrer">https://php.net/manual/en/migration53.deprecated.php</a>

"Deprecated features in PHP 5.3.x ...Comments starting with '#' are now deprecated in .INI files." 

There you have it. Hash '#' appears to remain as a comment option by default by not being deprecated. I plan to use it to distinguish various layers of nested if/else statements and mark their closing brackets, or use to distinguish code comments from commented out code as others have suggested in related posts. (Note: Link was valid/working as of 4/23/19, although who knows if it'll still be working when you're reading this.)

blocks|key|241575|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|241576|除了个人喜好之外，还有什么原因让评论使用//而不是#吗？|blockquote|241577|241578|241579|我自己来这里寻找答案，很高兴知道没有和代码的区别。|offset|length|style|BOLD|241580|然而，在偏好方面，人们可能会说，你更喜欢'shell->perl->php‘注释一致性而不是'c->php’方式。|241581|由于我确实将php作为穷人的webby+perl来处理，所以我使用#..然后我看到了别人的代码，就直接说到了这一点。;)|241582|entityMap^0|0|0|0|0|I|1|0|0|0^^$0|@$1|2|3|-4|4|5|6|R|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|S|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|U|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|V|7|@$H|W|I|X|J|K]]|8|@]|9|$]]|$1|L|3|M|4|5|6|Y|7|@]|8|@]|9|$]]|$1|N|3|O|4|5|6|Z|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|10|7|@]|8|@]|9|$]]]|Q|$]]

<blockquote>
 Is there any reason, aside from personal preference, to use // rather
 than # for comments?
</blockquote>

I came here for the answer myself, and its good to know there is NO code difference. 

However, preference-wise one could argue that you'd prefer the 'shell->perl->php' comment consistency vs the 'c->php' way.

Since I did approach php as a poor man's webby perl, I was using #.. and then I saw someone else's code and came straight to SO. ;)

blocks|key|2909983|text|OP问题：“除了个人喜好，还有什么理由使用//而不是#来进行评论吗？”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2909984|一个2021年的答案，当然不是我们在这个帖子中看到的唯一答案：|2909985|如果您正在使用Visual+Studio+code并使用区域来阻止您的代码，则必须使用#而不是//来定义区域。对于这个问题，不是，即使对于这个用例也是如此：如果你注释掉一个区域，你可以使用#、//或/**+*/，你使用的技术是个人偏好。|offset|length|style|CODE|BOLD|2909986|VSCode中的块定义示例：|2909987|#region+this+is+a+major+block
/**+DocBlock+*/
function+one()+{}
/**+DocBlock+*/
function+two()+{
++#region+nested+region+based+on+indentation
++//+comments+and+code+in+here
++++++#+another+nested+region+based+on+indentation
++++++++//+foo
++++++#endregion
++#endregion
}
#endregion|code-block|syntax|javascript|2909988|在内部块的折叠上：|2909989|#region+this+is+a+major+block
/**+DocBlock+*/
function+one()+{}
/**+DocBlock+*/
function+two()+{
>++#region+nested+region+based+on+indentation
}
#endregion|2909990|在外部块的折叠上：|2909991|>+#region+this+is+a+major+block|2909992|我列举了下面的具体用法，人们可能想尝试一下，但这些用法都不起作用。实际上，这正是您如何DISable一个#region块的方法：|2909993|//+#region
//+#endregion
/**+#region+*/
/**+#endregion+*/|2909994|关于在VSCode中注释掉一个区域：|2909995|/**+You+can+now+collapse+this+block
#region+Test1
//+foo
#endregion
//+everything+through+to+here+is+collapsed
*/

//+#region+Test1
//+folding+is+disabled+here
//+#endregion

#+#region+Test1
//+this+also+disables+the+fold
#+#endregion|2909996|尽管如此，“除了个人喜好，还有什么理由使用//而不是#来做评论呢？”我同意本文和other+thread中的注释：//更被认可和使用，这通常是使用这种注释样式而不是#的一个很好的理由。|2909997|最后，要注意基于缩进的嵌套，因为代码格式可以删除手动缩进，从而破坏基于注释的嵌套块方案。我已经用#和//+(顺便说一下，//也嵌套在缩进上)测试过这一点。同样，在OP问题的上下文中，没有理由在当前VSCode的此上下文中使用//而不是#进行嵌套缩进，因为两者的工作方式完全相同。但是，这是在//上使用#的用例。|2909998|Ref+-不需要扩展，在1.62.3中进行了验证。也可以在那里查看缩进说明。|2909999|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1935565/php-comments-vs|1|https://code.visualstudio.com/docs/editor/codebasics#_folding^0|0|0|17|1|1B|2|2M|1|2O|2|2R|6|26|A|0|0|0|0|0|0|0|0|0|0|0|1L|2|2A|1|14|C|0|0|1C|1|1E|2|1O|2|34|2|39|1|41|2|46|1|0|0|3|1|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1P|8|@$F|1Q|G|1R|H|I]|$F|1S|G|1T|H|I]|$F|1U|G|1V|H|I]|$F|1W|G|1X|H|I]|$F|1Y|G|1Z|H|I]|$F|20|G|21|H|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|22|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|23|8|@]|9|@]|A|$P|Q]]|$1|R|3|S|5|6|7|24|8|@]|9|@]|A|$]]|$1|T|3|U|5|O|7|25|8|@]|9|@]|A|$P|Q]]|$1|V|3|W|5|6|7|26|8|@]|9|@]|A|$]]|$1|X|3|Y|5|O|7|27|8|@]|9|@]|A|$P|Q]]|$1|Z|3|10|5|6|7|28|8|@]|9|@]|A|$]]|$1|11|3|12|5|O|7|29|8|@]|9|@]|A|$P|Q]]|$1|13|3|14|5|6|7|2A|8|@]|9|@]|A|$]]|$1|15|3|16|5|O|7|2B|8|@]|9|@]|A|$P|Q]]|$1|17|3|18|5|6|7|2C|8|@$F|2D|G|2E|H|I]|$F|2F|G|2G|H|I]]|9|@$F|2H|G|2I|1|2J]]|A|$]]|$1|19|3|1A|5|6|7|2K|8|@$F|2L|G|2M|H|I]|$F|2N|G|2O|H|I]|$F|2P|G|2Q|H|I]|$F|2R|G|2S|H|I]|$F|2T|G|2U|H|I]|$F|2V|G|2W|H|I]|$F|2X|G|2Y|H|I]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2Z|8|@]|9|@$F|30|G|31|1|32]]|A|$]]|$1|1D|3|-4|5|6|7|33|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]|1L|$5|1G|1H|1I|A|$1J|1M]]]]

OP Question: &quot;Is there any reason, aside from personal preference, to use // rather than # for comments?&quot;
One 2021 Answer, which is certainly not the only answer as we see in this thread:
If you're using Visual Studio Code and using regions to block your code, then you must use <code>#</code> rather than <code>//</code> to define the region. To the question, No, even for this use case : If you are commenting out a region, you can use <code>#</code> or <code>//</code> or <code>/** */</code>, the technique you use for this is personal preference.
Examples for block definition in VSCode :
<pre class="lang-php prettyprint-override"><code>#region this is a major block
/** DocBlock */
function one() {}
/** DocBlock */
function two() {
 #region nested region based on indentation
 // comments and code in here
 # another nested region based on indentation
 // foo
 #endregion
 #endregion
}
#endregion
</code></pre>
On Fold of the inner block:
<pre class="lang-php prettyprint-override"><code>#region this is a major block
/** DocBlock */
function one() {}
/** DocBlock */
function two() {
&gt; #region nested region based on indentation
}
#endregion
</code></pre>
On Fold of the outer block:
<pre class="lang-php prettyprint-override"><code>&gt; #region this is a major block
</code></pre>
I cite the following specific usage which one might be tempted to try, but these do not work. In fact this is exactly how you DISable a #region block:
<pre class="lang-php prettyprint-override"><code>// #region
// #endregion
/** #region */
/** #endregion */
</code></pre>
As to commenting out a region in VSCode:
<pre class="lang-php prettyprint-override"><code>/** You can now collapse this block
#region Test1
// foo
#endregion
// everything through to here is collapsed
*/

// #region Test1
// folding is disabled here
// #endregion

# #region Test1
// this also disables the fold
# #endregion
</code></pre>
All of that said, &quot;Is there any reason, aside from personal preference, to use // rather than # for comments?&quot; I agree with comments in this thread and in the <a href="https://stackoverflow.com/questions/1935565/php-comments-vs">other thread</a>: <code>//</code> is more commonly recognized and used, which is usually a good reason to use that comment style over <code>#</code>.
Final note, be careful about nesting based on indentation, as code formatting can remove your manual indentation and thus ruin your scheme of nested blocks based on comments. I've tested this with both <code>#</code> and <code>//</code> (which BTW, <code>//</code> nests on indentation too. Again, in context with the OP question, No, there is no reason to use <code>//</code> over <code>#</code> for nested indentation in this context in the current VSCode because both work exactly the same. However, this is a use case for using <code>#</code> over <code>//</code>.
<a href="https://code.visualstudio.com/docs/editor/codebasics#_folding" rel="nofollow noreferrer">Ref</a> - no extension required, verified in 1.62.3. See notes on indentation there as well.

blocks|key|2909643|text|PHP+5.3中不推荐使用带有"#“的注释。因此请始终使用//或/.../|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2909644|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|$]]

Comments with "#" are deprecated with PHP 5.3. So always use // or /.../

I have never, ever, seen a PHP file using hashes (<code>#</code>) for commenting. But today I realized that I actually can! I'm assuming there's a reason why everybody uses <code>//</code> instead though, so here I am.

Is there any reason, aside from personal preference, to use <code>//</code> rather than <code>#</code> for comments?

Can I use a hash sign (#) for commenting in PHP?

Visual Studio

解释器

我从来没有见过使用散列(#)进行注释的PHP文件。但今天我意识到我真的能做到！我假设每个人都使用//是有原因的，所以我在这里除了个人偏好之外，是否还有使用// # 而不是#进行评论的原因？

问我可以在PHP中使用散列符号(#)进行注释吗？
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以在PHP中使用散列符号(#)进行注释吗？EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以在PHP中使用散列符号(#)进行注释吗？
EN