blocks|key|1408901|text|它们是一样的，但是如果你的代码中有MVC，并且不想在你的代码中有很多回显，那么第二个是很棒的。例如，在我的.phtml文件(Zend+Framework)中，我将编写如下内容：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1408902|<?php+if($this->value):+?>
Hello
<?php+elseif($this->asd):+?>
Your+name+is:+<?=+$this->name+?>
<?php+else:+?>
You+don't+have+a+name.
<?php+endif;+?>|code-block|syntax|javascript|1408903|entityMap^0|1H|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

They are the same but the second one is great if you have MVC in your code and don't want to have a lot of echos in your code. For example, in my <code>.phtml</code> files (Zend Framework) I will write something like this:

<pre><code>&lt;?php if($this-&gt;value): ?&gt;
Hello
&lt;?php elseif($this-&gt;asd): ?&gt;
Your name is: &lt;?= $this-&gt;name ?&gt;
&lt;?php else: ?&gt;
You don't have a name.
&lt;?php endif; ?&gt;
</code></pre>

blocks|key|1408933|text|如果可能的话，我会使用第一个选项，不管新的选项是什么。语法是标准的，每个人都知道。它也是向后兼容的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1408934|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 would use the first option if at all possible, regardless of the new option. The syntax is standard and everyone knows it. It's also backwards compatible.

blocks|key|1408984|text|在我们公司，处理HTML的首选方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1408985|<?+if($condition)+{+?>
+++HTML+content+here
<?+}+else+{+?>
+++Other+HTML+content+here
<?+}+?>|code-block|syntax|javascript|1408986|最后，这真的是一个选择并坚持下去的问题。|1408987|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

At our company, the preferred way for handling HTML is:

<pre><code>&lt;? if($condition) { ?&gt;
 HTML content here
&lt;? } else { ?&gt;
 Other HTML content here
&lt;? } ?&gt;
</code></pre>

In the end, it really is a matter of choosing one and sticking with it.

blocks|key|1409033|text|您可以在以下官方文档中找到它：PHP:+Alternative+syntax+for+control+structures|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1409034|entityMap|0|LINK|mutability|MUTABLE|url|http://ca3.php.net/manual/en/control-structures.alternative-syntax.php^0|F|1A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Here's where you can find it in the official documentation: <a href="http://ca3.php.net/manual/en/control-structures.alternative-syntax.php" rel="noreferrer">PHP: Alternative syntax for control structures</a>

blocks|key|1623728|text|两者都是一样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623729|但是:如果你想在视图文件(MVC的V)中使用PHP作为模板语言，你可以使用这个替代语法来区分为实现业务逻辑(MVC的控制器和模型部分)和gui逻辑而编写的php代码。当然，它不是强制性的，你可以使用任何你喜欢的语法。|1623730|ZF使用这种方法。|1623731|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|$]]

Both are the same.

But:
If you want to use PHP as your templating language in your view files(the V of MVC) you can use this alternate syntax to distinguish between php code written to implement business-logic (Controller and Model parts of MVC) and gui-logic.
Of course it is not mandatory and you can use what ever syntax you like.

ZF uses that approach.

blocks|key|1409109|text|这两种语法在技术上没有区别。另一种语法并不新鲜；至少早在PHP4，甚至更早的时候就支持它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409110|您可能更喜欢另一种形式，因为它显式地说明了哪个控制结构正在结束:例如，endwhile只能终止一个while块，而如果您遇到一个大括号，它可以关闭任何东西。|offset|length|style|CODE|1409111|但是，如果您使用的编辑器对其他类似C的语法中的花括号有特殊支持，那么您可能更喜欢传统语法。例如，Vim支持多次击键，用于导航到匹配的大括号和以大括号分隔的块的开头和结尾。另一种语法会破坏编辑器特性。|1409112|entityMap^0|0|Z|8|1D|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

There is no technical difference between the two syntaxes. The alternative syntax is not new; it was supported at least as far back as PHP 4, and perhaps even earlier.

You might prefer the alternative form because it explicitly states which control structure is ending: <code>endwhile</code>, for example, can only terminate a <code>while</code> block, whereas if you encounter a brace, it could be closing anything.

You might prefer the traditional syntax, though, if you use an editor that has special support for braces in other C-like syntaxes. Vim, for example, supports several keystrokes for navigating to matching braces and to the starts and ends of brace-delimited blocks. The alternative syntax would break that editor feature.

blocks|key|1409122|text|我想这是个人喜好的问题。我个人使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409123|if($something){
+++++++$execute_something;
}|code-block|syntax|javascript|1409124|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I think it's a matter of preference. I personally use:

<pre><code>if($something){
 $execute_something;
}
</code></pre>

blocks|key|1623833|text|我个人真的很讨厌这种替代语法。关于大括号的一件好事是，大多数IDE、vim等都有括号突出显示。在我的文本编辑器中，我可以双击一个大括号，它会突出显示整个块，这样我就可以很容易地看到它的结束和开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623834|我不知道有哪一个编辑器可以突出显示endif、endforeach等。|1623835|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|$]]

I personally really hate the alternate syntax. One nice thing about the braces is that most IDEs, vim, etc all have bracket highlighting. In my text editor I can double click a brace and it will highlight the whole chunk so I can see where it ends and begins very easily.

I don't know of a single editor that can highlight endif, endforeach, etc.

blocks|key|1623870|text|我过去常常使用大括号，但现在由于代码的可读性和可访问性，我更喜欢使用这种简明的替代语法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623871|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 used to use the curly braces but now a days I prefer to use this short-hand alternative syntax because of code readability and accessibility.

blocks|key|1623937|text|它们在功能上确实是相同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623938|但是，如果endif离对应的if太远，我认为给它一个参考注释会更好。这样你就可以很容易地找到它是在哪里打开的。无论是哪种语言：|offset|length|style|CODE|1623939|if+(my_horn_is_red+or+her_umbrella_is_yellow)
{

++++//+...

++++//+let's+pretend+this+is+a+lot+of+code+in+the+middle

++++foreach+(day+in+week)+{
++++++++sing(a_different_song[day]);
++++}

++++//+...

}+//if+my_horn_is_red|code-block|syntax|javascript|1623940|这实际上适用于任何类似的“关闭的东西”！;)|1623941|此外，一般而言，编辑器更好地处理花括号，从某种意义上说，他们可以将您指向打开的位置。但即便如此，描述性评论的有效性也丝毫不会降低。|1623942|entityMap^0|0|5|5|E|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

They are indeed both the same, functionally.

But if the <code>endif</code> is getting too far from the correspondent <code>if</code> I think it's much better practice to give a referencing comment to it. Just so you can easily find where it was open. No matter what language it is:

<pre><code>if (my_horn_is_red or her_umbrella_is_yellow)
{

 // ...

 // let's pretend this is a lot of code in the middle

 foreach (day in week) {
 sing(a_different_song[day]);
 }

 // ...

} //if my_horn_is_red
</code></pre>

That actually applies to any analogous "closing thing"! ;)

Also, in general, editors deal better with curly brackets, in the sense they can point you to where it was open. But even that doesn't make the descriptive comments any less valid.

blocks|key|1409272|text|最后，您不希望查找以下代码行，然后不得不猜测它是从哪里开始的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409273|<?php+}+?>|code-block|syntax|javascript|1409274|它们在技术上和功能上是相同的。|1409275|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In the end you just don't want to be looking for the following line and then having to guess where it started:

<pre><code>&lt;?php } ?&gt;
</code></pre>

Technically and functionally they are the same.

blocks|key|1624071|text|这一切都取决于，就我个人而言，我更喜欢带有回显和大量缩进的传统语法，因为它更容易阅读。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1624072|<?php
++++if($something){
++++++++doThis();
++++}else{
++++++++echo+'<h1>Title</h1>
++++++++++++This+is+a+paragraph
++++++++++++and+another+paragraph';
++++}
?>|code-block|syntax|javascript|1624073|我同意alt语法使用不同的end子句更清晰，但如果没有文本编辑器突出显示的帮助，我真的很难处理它们，我只是不习惯看到这样的“压缩”代码：|1624074|<?php+if(+$this->isEnabledViewSwitcher()+):+?>
<p+class="view-mode">
++++<?php+$_modes+=+$this->getModes();+?>
++++<?php+if($_modes+&&+count($_modes)>1):+?>
++++<label><?php+echo+$this->__('View+as')+?>:</label>
++++<?php+foreach+($this->getModes()+as+$_code=>$_label):+?>
++++++++<?php+if($this->isModeActive($_code)):+?>
++++++++++++<strong+title="<?php+echo+$_label+?>"+class="<?php+echo+strtolower($_code);+?>"><?php+echo+$_label+?>&nbsp;
++++++++<?php+else:+?>
++++++++++++<a+href="<?php+echo+$this->getModeUrl($_code)+?>"+title="<?php+echo+$_label+?>"+class="<?php+echo+strtolower($_code);+?>"><?php+echo+$_label+?></a>&nbsp;
++++++++<?php+endif;+?>
++++<?php+endforeach;+?>
++++<?php+endif;+?>

<?php+endif;+?>|1624075|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

It all depends, personally I prefer the traditional syntax with echos and plenty of indentations, since it's just so much easier to read.

<pre><code>&lt;?php
 if($something){
 doThis();
 }else{
 echo '&lt;h1&gt;Title&lt;/h1&gt;
 &lt;p&gt;This is a paragraph&lt;/p&gt;
 &lt;p&gt;and another paragraph&lt;/p&gt;';
 }
?&gt;
</code></pre>

I agree alt syntax is cleaner with the different end clauses, but I really have a hard time dealing with them without help from text-editor highlighting, and I'm just not used to seeing "condensed" code like this:

<pre><code>&lt;?php if( $this-&gt;isEnabledViewSwitcher() ): ?&gt;
&lt;p class="view-mode"&gt;
 &lt;?php $_modes = $this-&gt;getModes(); ?&gt;
 &lt;?php if($_modes &amp;&amp; count($_modes)&gt;1): ?&gt;
 &lt;label&gt;&lt;?php echo $this-&gt;__('View as') ?&gt;:&lt;/label&gt;
 &lt;?php foreach ($this-&gt;getModes() as $_code=&gt;$_label): ?&gt;
 &lt;?php if($this-&gt;isModeActive($_code)): ?&gt;
 &lt;strong title="&lt;?php echo $_label ?&gt;" class="&lt;?php echo strtolower($_code); ?&gt;"&gt;&lt;?php echo $_label ?&gt;&lt;/strong&gt;&amp;nbsp;
 &lt;?php else: ?&gt;
 &lt;a href="&lt;?php echo $this-&gt;getModeUrl($_code) ?&gt;" title="&lt;?php echo $_label ?&gt;" class="&lt;?php echo strtolower($_code); ?&gt;"&gt;&lt;?php echo $_label ?&gt;&lt;/a&gt;&amp;nbsp;
 &lt;?php endif; ?&gt;
 &lt;?php endforeach; ?&gt;
 &lt;?php endif; ?&gt;
&lt;/p&gt;
&lt;?php endif; ?&gt;
</code></pre>

blocks|key|1624140|text|我认为这真的取决于你个人的编码风格。如果你习惯了C%2B%2B，Javascript等，你可能会觉得使用{}语法更舒服。如果您习惯于Visual+Basic，则可能需要使用If+:+endif；语法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1624141|我不能确定其中一个比另一个更容易阅读--这是个人喜好。我通常这样做：|1624142|<?php
if+($foo)+{+?>
+++Foo!<?php
}+else+{+?>
+++Bar!<?php
}++//+if-else+($foo)+?>|code-block|syntax|javascript|1624143|这是不是更容易阅读：|1624144|<?php
if+($foo):+?>
+++Foo!<?php
else:+?>
+++Bar!<?php
endif;+?>|1624145|是一个见仁见智的问题。我能理解为什么有些人会觉得第二种方法更容易--但前提是你一生都没有用Javascript和C%2B%2B编程。:)|1624146|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I think that it really depends on your personal coding style.
If you're used to C++, Javascript, etc., you might feel more comfortable using the {} syntax.
If you're used to Visual Basic, you might want to use the if : endif; syntax.

I'm not sure one can definitively say one is easier to read than the other - it's personal preference. I usually do something like this:

<pre><code>&lt;?php
if ($foo) { ?&gt;
 &lt;p&gt;Foo!&lt;/p&gt;&lt;?php
} else { ?&gt;
 &lt;p&gt;Bar!&lt;/p&gt;&lt;?php
} // if-else ($foo) ?&gt;
</code></pre>

Whether that's easier to read than:

<pre><code>&lt;?php
if ($foo): ?&gt;
 &lt;p&gt;Foo!&lt;/p&gt;&lt;?php
else: ?&gt;
 &lt;p&gt;Bar!&lt;/p&gt;&lt;?php
endif; ?&gt;
</code></pre>

is a matter of opinion. I can see why some would feel the 2nd way is easier - but only if you haven't been programming in Javascript and C++ all your life. :)

blocks|key|1409487|text|我过去常常用大括号表示"if，else“条件。但是，我发现"+if+(xxx)：endif;“如果代码包装得很严密，在任何编辑器中都更容易阅读。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409488|当然，当大括号被选中时，许多编辑器都能够识别并突出显示代码块。有些人在"if(xxx)：endif“对上也做得很好(例如，NetBeans)|1409489|就我个人而言，我会推荐"if(xxx)：endif"，但对于小的条件检查(例如，只有一行代码)，没有太大的区别。|1409490|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|$]]

I used to use curly brackets for "if, else" conditions. However, I found "if(xxx): endif;" is more semantic if the code is heavily wrapped and easier to read in any editors.

Of course, lots editors are capable of recognise and highlight chunks of code when curly brackets are selected. Some also do well on "if(xxx): endif" pair (eg, NetBeans)

Personally, I would recommend "if(xxx): endif", but for small condition check (eg, only one line of code), there are not much differences.

blocks|key|1624283|text|我认为当您在视图脚本中混合使用ifs、fors和foreaches时，这一点尤其明显：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1624284|<?php+if+(+$this->hasIterable+):+?>
++++<h2>Iterable</h2>
++++<ul>
++++<?php+foreach+(+$this->iterable+as+$key+=>+$val+):?>
++++++++<?php+for+(+$i+=+0;+$i+<=+$val;+$i%2B%2B+):+?>
++++++++<li><?php+echo+$key+?></li>
++++++++<?php+endfor;+?>
++++<?php+endforeach;+?>
++++</ul>
<?php+elseif+(+$this->hasScalar+):+?>
++++<h2>Scalar</h2>
++++<?php+for+(+$i+=+0;+$i+<=+$this->scalar;+$i%2B%2B+):+?>
++++Foo+=+Bar
++++<?php+endfor;+?>
<?php+else:+?>
++++<h2>Other</h2>
++++<?php+if+(+$this->otherVal+===+true+):+?>
++++Spam
++++<?php+else:+?>++
++++Eggs++
++++<?php+endif;+?>
<?php+endif;+?>|code-block|syntax|javascript|1624285|与此相对的是：|1624286|<?php+if+(+$this->hasIterable+){+?>
++++<h2>Iterable</h2>
++++<ul>
++++<?php+foreach+(+$this->iterable+as+$key+=>+$val+){?>
++++++++<?php+for+(+$i+=+0;+$i+<=+$val;+$i%2B%2B+){+?>
++++++++<li><?php+echo+$key+?></li>
++++++++<?php+}+?>
++++<?php+}+?>
++++</ul>
<?php+}+elseif+(+$this->hasScalar+){+?>
++++<h2>Scalar</h2>
++++<?php+for+(+$i+=+0;+$i+<=+$this->scalar;+$i%2B%2B+){+?>
++++Foo+=+Bar
++++<?php+}+?>
<?php+}+else+{+?>
++++<h2>Other</h2>
++++<?php+if+(+$this->otherVal+===+true+){+?>
++++Spam
++++<?php+}+else+{+?>++
++++Eggs++
++++<?php+}+?>
<?php+}+?>|1624287|这对于长控制语句特别有用，因为在长控制语句中，您可能无法从下大括号看到顶部声明。|1624288|entityMap^0|F|2|J|3|O|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

I think that it's particularly clearer when you're using a mix of <code>if</code>s, <code>for</code>s and <code>foreach</code>es in view scripts:

<pre><code>&lt;?php if ( $this-&gt;hasIterable ): ?&gt;
 &lt;h2&gt;Iterable&lt;/h2&gt;
 &lt;ul&gt;
 &lt;?php foreach ( $this-&gt;iterable as $key =&gt; $val ):?&gt;
 &lt;?php for ( $i = 0; $i &lt;= $val; $i++ ): ?&gt;
 &lt;li&gt;&lt;?php echo $key ?&gt;&lt;/li&gt;
 &lt;?php endfor; ?&gt;
 &lt;?php endforeach; ?&gt;
 &lt;/ul&gt;
&lt;?php elseif ( $this-&gt;hasScalar ): ?&gt;
 &lt;h2&gt;Scalar&lt;/h2&gt;
 &lt;?php for ( $i = 0; $i &lt;= $this-&gt;scalar; $i++ ): ?&gt;
 &lt;p&gt;Foo = Bar&lt;/p&gt;
 &lt;?php endfor; ?&gt;
&lt;?php else: ?&gt;
 &lt;h2&gt;Other&lt;/h2&gt;
 &lt;?php if ( $this-&gt;otherVal === true ): ?&gt;
 &lt;p&gt;Spam&lt;/p&gt;
 &lt;?php else: ?&gt; 
 &lt;p&gt;Eggs&lt;/p&gt; 
 &lt;?php endif; ?&gt;
&lt;?php endif; ?&gt;
</code></pre>

as opposed to:

<pre><code>&lt;?php if ( $this-&gt;hasIterable ){ ?&gt;
 &lt;h2&gt;Iterable&lt;/h2&gt;
 &lt;ul&gt;
 &lt;?php foreach ( $this-&gt;iterable as $key =&gt; $val ){?&gt;
 &lt;?php for ( $i = 0; $i &lt;= $val; $i++ ){ ?&gt;
 &lt;li&gt;&lt;?php echo $key ?&gt;&lt;/li&gt;
 &lt;?php } ?&gt;
 &lt;?php } ?&gt;
 &lt;/ul&gt;
&lt;?php } elseif ( $this-&gt;hasScalar ){ ?&gt;
 &lt;h2&gt;Scalar&lt;/h2&gt;
 &lt;?php for ( $i = 0; $i &lt;= $this-&gt;scalar; $i++ ){ ?&gt;
 &lt;p&gt;Foo = Bar&lt;/p&gt;
 &lt;?php } ?&gt;
&lt;?php } else { ?&gt;
 &lt;h2&gt;Other&lt;/h2&gt;
 &lt;?php if ( $this-&gt;otherVal === true ){ ?&gt;
 &lt;p&gt;Spam&lt;/p&gt;
 &lt;?php } else { ?&gt; 
 &lt;p&gt;Eggs&lt;/p&gt; 
 &lt;?php } ?&gt;
&lt;?php } ?&gt;
</code></pre>

This is especially useful for long control statements where you might not be able to see the top declaration from the bottom brace.

blocks|key|1409638|text|我觉得已经存在的答案都不能完全确定这里的答案，所以我将阐明我自己的观点。在功能上，这两种方法是相同的。如果程序员熟悉遵循C语法的其他语言，那么他们可能会对大括号感到更舒服，或者如果php是他们学习的第一种语言，他们会对if+endif语法感到更舒服，因为它看起来更接近于常规语言。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1409639|如果您是一位非常认真的程序员，并且需要快速完成任务，那么我确实认为花括号语法更好，因为它节省了输入时间|1409640|if(/*condition*/){
++++/*body*/+
}|code-block|syntax|javascript|1409641|与|1409642|if(/*condition*/):
++++/*body*/
endif;|1409643|这在其他循环中尤其如此，比如foreach，在这些循环中，您最终会额外键入10个字符。使用大括号，你只需要输入两个字符，但是对于基于关键字的语法，你必须为每个循环和条件语句输入一个完整的额外关键字。|1409644|entityMap^0|31|2|34|5|0|0|0|0|0|E|7|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|T|$]]

I feel that none of the preexisting answers fully identify the answer here, so I'm going to articulate my own perspective. Functionally, the two methods are the same. If the programer is familiar with other languages following C syntax, then they will likely feel more comfortable with the braces, or else if php is the first language that they're learning, they will feel more comfortable with the <code>if</code> <code>endif</code> syntax, since it seems closer to regular language.

If you're a really serious programmer and need to get things done fast, then I do believe that the curly brace syntax is superior because it saves time typing

<pre><code>if(/*condition*/){
 /*body*/ 
}
</code></pre>

compared to

<pre><code>if(/*condition*/):
 /*body*/
endif;
</code></pre>

This is especially true with other loops, say, a <code>foreach</code> where you would end up typing an extra 10 chars. With braces, you just need to type two characters, but for the keyword based syntax you have to type a whole extra keyword for every loop and conditional statement.

Are there any differences between...

<pre><code>if ($value) {

}
</code></pre>

...and...

<pre><code>if ($value):

endif;
</code></pre>

?

Difference between if () { } and if () : endif;

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在…之间有什么不同吗？if ($value) {}...and...if ($value):endif;

问if () {}和if ()的区别: endif；
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问if () {}和if ()的区别: endif；EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问if () {}和if ()的区别: endif；
EN