mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 08:58:56 +00:00
rewording to simplify the text
thanks for the hint :) git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@213654 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
1de8712abe
commit
e07050a924
1 changed files with 5 additions and 6 deletions
|
@ -1,5 +1,5 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.14 $ -->
|
||||
<!-- $Revision: 1.15 $ -->
|
||||
<!-- splitted from ./en/functions/misc.xml, last change in rev 1.58 -->
|
||||
<refentry id="function.eval">
|
||||
<refnamediv>
|
||||
|
@ -17,10 +17,8 @@
|
|||
<parameter>code_str</parameter> as PHP code. Among other things,
|
||||
this can be useful for storing code in a database text field for
|
||||
later execution. <parameter>code_str</parameter> does not have to
|
||||
start with or contain <link linkend="language.basic-syntax.phpmode">
|
||||
PHP Opening tags</link>. If you want your given string to be
|
||||
evaluated like regular PHP code with opening tags you can prepend
|
||||
<parameter>code_str</parameter> with a closing tag.
|
||||
contain <link linkend="language.basic-syntax.phpmode"> PHP Opening
|
||||
tags</link>.
|
||||
</simpara>
|
||||
<simpara>
|
||||
There are some factors to keep in mind when using
|
||||
|
@ -28,7 +26,8 @@
|
|||
be valid PHP code, including things like terminating statements
|
||||
with a semicolon so the parser doesn't die on the line after the
|
||||
<function>eval</function>, and properly escaping things in
|
||||
<parameter>code_str</parameter>.
|
||||
<parameter>code_str</parameter>. To mix HTML output and PHP code
|
||||
you can use a closing PHP tag to leave PHP mode.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Also remember that variables given values under
|
||||
|
|
Loading…
Reference in a new issue