rfc:shortags
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:shortags [2008/04/03 20:56] – stas | rfc:shortags [2011/05/19 16:34] – rasmus | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2008-04-03 | * Date: 2008-04-03 | ||
* Author: Stas Malyshev < | * Author: Stas Malyshev < | ||
- | * Status: | + | * Status: |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
Line 29: | Line 23: | ||
The second form looks much nicer and cleaner, and can be easily understood and edited by non-PHP people like graphical designers, copy editors, etc. However, to use this form, the **short_open_tag** INI setting should be enabled. When this tag is enabled, **<?** also is treated as PHP starting tag, which may be a problem for people using XML in templates, since the engine would confuse XML starting tag with PHP code start. | The second form looks much nicer and cleaner, and can be easily understood and edited by non-PHP people like graphical designers, copy editors, etc. However, to use this form, the **short_open_tag** INI setting should be enabled. When this tag is enabled, **<?** also is treated as PHP starting tag, which may be a problem for people using XML in templates, since the engine would confuse XML starting tag with PHP code start. | ||
+ | |||
==== Proposals ==== | ==== Proposals ==== | ||
Line 39: | Line 34: | ||
* **Pro**: Allows the setting to be controlled locally without the user needing to do any administration or configuration | * **Pro**: Allows the setting to be controlled locally without the user needing to do any administration or configuration | ||
- | * **Contra**: If the setting " | + | * **Contra**: If the setting " |
=== Always available template tags === | === Always available template tags === |
rfc/shortags.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1