diff options
author | Derek Jones <derek.jones@ellislab.com> | 2011-10-05 22:12:27 +0200 |
---|---|---|
committer | Derek Jones <derek.jones@ellislab.com> | 2011-10-05 22:13:39 +0200 |
commit | 36907daf461ae64e09a6de004e1f80c7e4daefec (patch) | |
tree | 7e68b78fff5ffa5b8ab8d4d8b270ac19db375c1b /user_guide_src | |
parent | 4f0c8cb509f1a16e62bc1ddf23d035fcb06e0214 (diff) |
fixed code blocks in at_a_glance (finishes overview folder code block cleanup)
Diffstat (limited to 'user_guide_src')
-rw-r--r-- | user_guide_src/source/overview/at_a_glance.rst | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/user_guide_src/source/overview/at_a_glance.rst b/user_guide_src/source/overview/at_a_glance.rst index df4e3ca06..31f0b4dd9 100644 --- a/user_guide_src/source/overview/at_a_glance.rst +++ b/user_guide_src/source/overview/at_a_glance.rst @@ -80,11 +80,19 @@ simply can not match the performance of native PHP, and the syntax that must be learned to use a template engine is usually only marginally easier than learning the basics of PHP. Consider this block of PHP code:: - <ul> <?php foreach ($addressbook as $name):?> <li><?=$name?></li> <?php endforeach; ?> </ul> + <ul> + <?php foreach ($addressbook as $name):?> + <li><?=$name?></li> + <?php endforeach; ?> + </ul> Contrast this with the pseudo-code used by a template engine:: - <ul> {foreach from=$addressbook item="name"} <li>{$name}</li> {/foreach} </ul> + <ul> + {foreach from=$addressbook item="name"} + <li>{$name}</li> + {/foreach} + </ul> Yes, the template engine example is a bit cleaner, but it comes at the price of performance, as the pseudo-code must be converted back into PHP |