cvs: phpdoc /kr/appendices debugger.xml phpdevel.xml regexp.xml /kr/chapters intro.xml
| From: | Younsoo Kim | Date: | Fri, 19 Jan 2001 05:26:39 +0000 |
| Subject: | cvs: phpdoc /kr/appendices debugger.xml phpdevel.xml regexp.xml /kr/chapters intro.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969333735@lists.php.net to get a copy of this message | ||
corean Thu Jan 18 21:26:39 2001 EDT
Modified files:
/phpdoc/kr/appendices debugger.xml phpdevel.xml regexp.xml
/phpdoc/kr/chapters intro.xml
Log:
PR:
Submitted by:
Reviewed by:
Obtained from:
Index: phpdoc/kr/appendices/debugger.xml diff -u phpdoc/kr/appendices/debugger.xml:1.3 phpdoc/kr/appendices/debugger.xml:1.4 --- phpdoc/kr/appendices/debugger.xml:1.3 Thu Jan 11 20:10:47 2001 +++ phpdoc/kr/appendices/debugger.xml Thu Jan 18 21:26:38 2001 @@ -1,63 +1,54 @@ <appendix id="debugger"> <title>The PHP Debugger</title> <sect1 id="debugger-using"> - <title>Using the Debugger</title> + <title>ëë²ê±° ì¬ì©ê¸°</title> <para> - PHP's internal debugger is useful for tracking down evasive bugs. - The debugger works by connecting to a <acronym>TCP</acronym> port - for every time PHP starts up. All error messages from that - request will be sent to this TCP connection. This information is - intended for "debugging server" that can run inside an - <acronym>IDE</acronym> or programmable editor (such as Emacs). + PHPì ë´ë¶ ëë²ê±°ë ìììë ë¤ì´ ë²ê·¸ë¤ì ì ì©íë¤. + ì´ ëë²ê±°ë PHPê° ìëíë ëì ë´ë´ <acronym>TCP</acronym> í¬í¸ì ì ìí´ì ìì ëë¤. + ìì²(Request)ë TCPì ìì ë³´ë´ì 모ë ìë¬ ë©ì¸ì§ê° ëì¨ë¤. + <acronym>IDE</acronym>ë Progrmmable ìëí° ììì ì¤íëë "ëë²ê¹ ìë²(Debugging server"ì ê°ì ì ì¸ ì ë³´ì´ë¤(Emacsì²ë¼). + </para> <para> - How to set up the debugger: + ëë²ê±° ì¤ì¹íë ë°©ë²: <orderedlist> <listitem> <simpara> - Set up a TCP port for the debugger in the <link linkend="configuration.file">configuration file</link> (<link linkend="ini.debugger.port">debugger.port</link>) and enable it - (<link linkend="ini.debugger.enabled">debugger.enabled</link>). + ëë²ê±°ë¥¼ ìí TCP í¬í¸ ì¤ì¹ë <link linkend="configuration.file">configuration file</link>ìì ìë¤. + (<link linkend="ini.debugger.port">debugger.port</link>)ê³¼ ê°ë¥ì¤ì (<link linkend="ini.debugger.enabled">debugger.enabled</link>) </simpara> </listitem> <listitem> <simpara> - Set up a TCP listener on that port somewhere (for example + ì´ëê°ì í¬í¸ìì TCP ê°ìì(lestener) ì¤ì¹ (ì를 ë¤ì´ <command>socket -l -s 1400</command> on UNIX). </simpara> </listitem> <listitem> <simpara> - In your code, run - "debugger_on(<replaceable>host</replaceable>)", where - <replaceable>host</replaceable> is the IP number or name of the - host running the <acronym>TCP</acronym> listener. +ë¹ì ì ì½ëìì íê³ , +<acronym>TCP</acronym> ê°ìì(listener)ê° ì¤í´ëë ëì <replaceable>host</replaceable>ë IP ì«ìì í¸ì¤í¸ì ì´ë¦ì ê°ì§ <replaceable>host</replaceable>ìì "debugger_on(<replaceable>host</replaceable>)"ì ì¤í. </simpara> </listitem> </orderedlist> - Now, all warnings, notices etc. will show up on that listener - socket, <emphasis>even if you them turned off with - <function>error_reporting</function> - </emphasis>. + 모ë ê²½ê³ ë ê°ìì ìì¼(listener socket)ë ê³µì§ëë¤. + <emphasis>ë¹ë¡ <function>error_reporting</function>ì ìí´ êº¼ì ¸ìëë¼ë</emphasis>. </para> <note> <para> - The code for the debugger has not been ported to PHP 4, at the - present time only PHP 3 supports the debugger code. - </para> + ëë²ê±°ë¥¼ ìí ì½ë PHP4ììë ì ê³µëì§ ìëë¤. ì´ê²ì PHP3ììë§ ì ê³µëë¤. + </para> </note> </sect1> <sect1 id="debugger-protocol"> - <title>Debugger Protocol</title> + <title>ëë²ê±° íë¡í ì½(Debugger Protocl)</title> <para> - The debugger protocol is line-based. Each line has a - <emphasis>type</emphasis>, and several lines compose a - <emphasis>message</emphasis>. Each message starts with a line of - the type <literal>start</literal> and terminates with a line of - the type <literal>end</literal>. PHP may send lines for different - messages simultaneously. + ëë²ê±° íë¡ì½í¨ì ë¼ì¸ 기ë°ì´ë¤. ê° ë¼ì¸ì <emphasis>type</emphasis>ê³¼ <emphasis>message</emphasis>ë¡ ì´ë£¨ì´ì§ ëªëª ë¼ì¸ë¤ì ê°ì§ë¤. + ê° ë©ì¸ì§ë <literal>start</literal>íì ì ë¼ì¸ì¼ë¡ ììëê³ , <literal>end</literal>íì ì ë¼ì¸ì¼ë¡ ìí´ ì¤ì§ëë¤. + PHPë ìë§ ì¼ì í ë¤ë¥¸ ë©ì¸ì§ë¤ì ë¼ì¸ë¤ì ë³´ë¼ê²ì´ë¤. </para> <para> - A line has this format: +ê° ë¼ì¸ì ë¤ìì í¬ë§·ì ê°ì§ë¤: <informalexample> <literallayout> <replaceable>date</replaceable> Index: phpdoc/kr/appendices/phpdevel.xml diff -u phpdoc/kr/appendices/phpdevel.xml:1.3 phpdoc/kr/appendices/phpdevel.xml:1.4 --- phpdoc/kr/appendices/phpdevel.xml:1.3 Thu Jan 11 20:10:47 2001 +++ phpdoc/kr/appendices/phpdevel.xml Thu Jan 18 21:26:38 2001 @@ -18,14 +18,12 @@ <sect2 id="phpdevel-addfunc-args"> <title>í¨ì ì¸ì</title> <para> - - Arguments are always of type pval. This type contains a union - which has the actual type of the argument. So, if your function - takes two arguments, you would do something like the following at - the top of your function:</para> +ì¸ìë ì¸ì ë pvalíì ì´ë¤. ì´ íì ì ì¸ìì ì¤ì íì (actual type)ì ê²°í©ì í¬í¨íë¤. +ê·¸ëì, ë¹ì ì í¨ìê° 2ê°ì ì¸ì를 ê°ì§ë¤ë©´ ë¹ì ì ë¹ì ì í¨ì 맨ììì ë°ë¥´ëê²ì²ë¼ í´ì¼ í ê²ì´ë¤: +</para> <para> <example> - <title>Fetching function arguments</title> + <title>í¨ì ì¸ì ê°ì ¸ì¤ê¸°</title> <programlisting> pval *arg1, *arg2; if (ARG_COUNT(ht) != 2 || getParameters(ht,2,&arg1,&arg2)==FAILURE) { @@ -33,33 +31,32 @@ } </programlisting> </example> - - NOTE: Arguments can be passed either by value or by reference. In - both cases you will need to pass &(pval *) to getParameters. If - you want to check if the n'th parameter was sent to you by - reference or not, you can use the function, - ParameterPassedByReference(ht,n). It will return either 1 or 0.</para> - <simpara> - When you change any of the passed parameters, whether they are - sent by reference or by value, you can either start over with the - parameter by calling pval_destructor on it, or if it's an ARRAY - you want to add to, you can use functions similar to the ones in - internal_functions.h which manipulate return_value as an ARRAY.</simpara> - <simpara> - Also if you change a parameter to IS_STRING make sure you first - assign the new estrdup()'ed string and the string length, and only - later change the type to IS_STRING. If you change the string of a - parameter which already IS_STRING or IS_ARRAY you should run - pval_destructor on it first.</simpara> +ë ¸í¸ : í¨ìë ê°ì´ë 참조 ëì¤ íëë¡ ì¸ì를 ë길ì ìë¤. +ì쪽 ê²½ì°ë¤ ë¹ì ì &(pval *) ìì getParametersë¡ íµê³¼íëê² íìí ê²ì´ë¤. +ë¹ì ì´ ì²´í¬íê² ë¤ë©´ ëªë²ì§¸ ì¸ìê° ë¹ì ìê² ì°¸ì¡°ê°ì´ë ìëê²ì¼ë¡ ë³´ë´ì§ëì§ +ìë¤ë©´ í¨ììì ì¬ì©í ì ìë¤. +ParameterPassedByReference(ht,n). 그건 1ì´ë 0 ê°ì ë°ííë¤. +</para> + <simpara> +ë¹ì ì ëê²¨ì¨ ì¸ìì ì´ë¤ê²ì ë³ê²½í ë ê·¸ë¤ì 참조ë ê°ì ìí´ ë³´ë¼ì§ ìëì§ +pval_destuctor ë¼ ë¶ë¦¬ì´ ì¸ì를 ììíê±°ë, ë§ì½ ë°°ì´ì´ë¼ë©´ ì¶ê°í ë í¨ì ë¹ì«íê² +ë°°ì´ê°ì ë°íê°ì ë¤ë£¨ë internal_functions.hë´ìì ì¬ì©í ì ìë¤ +</simpara> + <simpara> +ì´ë¯¸ ë¹ì ì IS_STRINGì¼ë¡ ì¸ì를 ë°ê¾¼ë¤ë©´ ìë¡ì´ estrdup()ìë 문ìì´, 문ìì´ ê¸¸ì´, +ê°ì¥ ëì¤ì ë°ê¾¼ IS_STRINGì íì ì 먼ì í ë¹íë ê²ì íì¤í í´ì¼ íë¤. +ì´ë¯¸ ì¡´ì¬íë IS_STRINGì´ë IS_ARRAYê°ì ì¸ìì 문ìì´ì ë°ê¾¼ë¤ë©´ +pval_destructor를 먼ì ì¤íí´ì¼ í ê²ì´ë¤.</simpara> </sect2> <sect2 id="phpdevel-addfunc-varargs"> - <title>Variable Function Arguments</title> + <title>ë³ìí í¨ì í본</title> <para> - A function can take a variable number of arguments. If your function can - take either 2 or 3 arguments, use the following:</para> +ì´ í¨ìë í본ì ë³ìí ì«ì ê°ì§ ì ìë¤. +ë¹ì ì í¨ìê° 2ê°ë 3ê°ì ì¸ì를 ê°ì§ì ìë¤ë©´ ë¤ìê³¼ ê°ì´ ì¬ì©íë¼: +</para> <para> <example> - <title>Variable function arguments</title> + <title>ë³ìí í¨ì ì¸ì</title> <programlisting> pval *arg1, *arg2, *arg3; int arg_count = ARG_COUNT(ht); @@ -73,13 +70,11 @@ </para> </sect2> <sect2 id="phpdevel-addfunc-using-args"> - <title>Using the Function Arguments</title> + <title>í¨ì ì¸ì ì¬ì©í기</title> <para> - The type of each argument is stored in the pval type field. This - type can be any of the following: - +ê° ì¸ìì íì ì pvalíì íëë¡ ì ì¥ëë¤. ì´ íì ì ë¤ìì¤ ì´ëê²ì´ë ì¬ì©í ì ìë¤: <table> - <title>PHP Internal Types</title> + <title>PHP ë´ë¶ íì ë¤</title> <tgroup cols="2"> <tbody> <row> @@ -123,11 +118,9 @@ </table> </para> <para> - If you get an argument of one type and would like to use it as - another, or if you just want to force the argument to be of a - certain type, you can use one of the following conversion - functions: - +ë¹ì ì´ íëì íì ì¸ì ê°ì§ë ê²ê³¼ ë¤ë¥¸ ê²ì²ë¼ ì¬ì©í길 ë°ë¼ë ê² ëë +ë¨ì§ íì¤í íì ì ì¸ì를 ìíí길 ìíë¤ë©´, +ë¹ì ì ì íí¨ìë¤ ì¤ íë를 ì¸ì ìë¤: <programlisting> convert_to_long(arg1); convert_to_double(arg1); @@ -137,9 +130,9 @@ </programlisting> </para> <simpara> - These function all do in-place conversion. They do not return anything.</simpara> +ì´ë¤ í¨ìë 모ë íëë¡ ë³í를 íë¤. ìë¬´ë° ë°íì íì§ ìëë¤.</simpara> <para> - The actual argument is stored in a union; the members are: +ì¤ì ì ì¸ ì¸ìë ê²°í©ì²´ë¡ ì ì¥ëë¤; ê·¸ 구ì±ìì: <itemizedlist> <listitem> <simpara>IS_STRING: arg1->value.str.val</simpara> @@ -154,26 +147,23 @@ </para> </sect2> <sect2 id="phpdevel-addfunc-memmgmt"> - <title>Memory Management in Functions</title> + <title>í¨ìë´ ë©ëª¨ë¦¬ ê´ë¦¬</title> + <simpara> +모ë ë©ëª¨ë¦¬ë emalloc()ì´ë estrdup()ë¡ í ë¹ëë í¨ìê° íìíë¤. +ì´ê²ë¤ì malloc()ì strdup()í¨ìê³¼ ê°ì´ ë³´ì´ë ë©ëª¨ë¦¬ì²ë¦¬ê°ìí¨ìì´ë¤. +ë©ëª¨ë¦¬ë efree()ë¡ í´ì ë ì ìë¤. +</simpara> + <simpara> +ì´ íë¡ê·¸ë¨ë´ìì ë ì¢ ë¥ì ë©ëª¨ë¦¬ë: +ë³ìíìì íì를 ë°ííë ê²ê³¼ ë¹ì ì´ ë´ë¶ í¨ìë´ íìí ìì 기ìµì¥ì. +ë¹ì ì´ ë¬¸ìì´ì ë³ìíì¼ë¡ ì§ì í ë +ë°íë íìê° emalloc()ë estrdup()ì 먼ì ë©ëª¨ë¦¬ì í ë¹ëìëì§ íì¸í´ì¼ íë¤. +</simpara> <simpara> - Any memory needed by a function should be allocated with either - emalloc() or estrdup(). These are memory handling abstraction - functions that look and smell like the normal malloc() and - strdup() functions. Memory should be freed with efree().</simpara> - <simpara> - There are two kinds of memory in this program: memory which is - returned to the parser in a variable, and memory which you need for - temporary storage in your internal function. When you assign a - string to a variable which is returned to the parser you need to - make sure you first allocate the memory with either emalloc() or - estrdup(). This memory should NEVER be freed by you, unless you - later in the same function overwrite your original assignment - (this kind of programming practice is not good though).</simpara> - <simpara> - For any temporary/permanent memory you need in your - functions/library you should use the three emalloc(), estrdup(), - and efree() functions. They behave EXACTLY like their counterpart - functions. Anything you emalloc() or estrdup() you have to efree() +ì´ë¤ ìì/ ì구 ë©ëª¨ë¦¬ë¥¼ ìí´ ë¹ì ì ë¹ì ì í¨ì/ë¼ì´ë¸ë¬ë¦¬ë´ìì emalloc(), estrdup(), ê·¸ë¦¬ê³ efree() í¨ì 3ê°ë¥¼ ì´ì©í´ì¼ íë¤. +ë¹ì ì ì¬ë³¸ í¨ìì²ë¼ ì íí í´ì¼ í ê²ì´ë¤. + + Anything you emalloc() or estrdup() you have to efree() at some point or another, unless it's supposed to stick around until the end of the program; otherwise, there will be a memory leak. The meaning of "the functions behave exactly like their @@ -181,16 +171,13 @@ emalloc()'ed nor estrdup()'ed you might get a segmentation fault. So please take care and free all of your wasted memory.</simpara> <simpara> - If you compile with "-DDEBUG", PHP 3 will print out a list of all - memory that was allocated using emalloc() and estrdup() but never - freed with efree() when it is done running the specified script.</simpara> +ë§ì½ ë¹ì ì´ "-DDEBUG"ë¡ ì»´íì¼íë¤ë©´ PHP3ë ì§ì ë emalloc()ê³¼ estrdup() ì¬ì©í 모ë ë©ëª¨ë¦¬ 리ì¤í¸ë¥¼ ì¶ë ¥í ê²ì´ë¤. ëª ìë ì¤í¬ë¦½í¸ê° ì¤íëê³ ììëë efree()를 ì©í í´ì 를 í´ì ìëë¤. +</simpara> </sect2> <sect2 id="phpdevel-addfunc-symtab"> - <title>Setting Variables in the Symbol Table</title> + <title>ì¬ë³¼ í ì´ë¸ìì ë³ìí ì¤ì </title> <para> - A number of macros are available which make it easier to set a - variable in the symbol table: - + 매í¬ë¡ë¤ì ì«ìë ì¬ë³¼ í ì´ë¸ìì ë ì½ê² ë³ìíì¼ë¡ ì¤ì í ì ìë¤: <itemizedlist> <listitem> <simpara>SET_VAR_STRING(name,value) <footnoteref linkend="symtab-1"/> @@ -207,52 +194,51 @@ <para> <footnote id="symtab-1"> <simpara> - Be careful here. The value part must be malloc'ed manually because - the memory management code will try to free this pointer later. Do - not pass statically allocated memory into a SET_VAR_STRING.</simpara> +ì´ë¶ë¶ì 주ìê¹ê² ë³´ë¼ +ì´ ê°ì ìëì¼ë¡ mallocíì´ì¼ íë¤. ìëíë©´ ë©ëª¨ë¦¬ ê´ë¦¬ ì½ëë ëì¤ì ì´ ë¶ë¶ì +í´ì í ê²ì´ë¤. SET_VAR_STRINGë¡ë¶í° ì§ì ë ë©ëª¨ë¦¬ë¥¼ ì ì ì¼ë¡ ëì§ ë§ìì¼ íë¤.</simpara> </footnote> </para> <simpara> - Symbol tables in PHP 3.0 are implemented as hash tables. At any - given time, &symbol_table is a pointer to the 'main' symbol - table, and active_symbol_table points to the currently active - symbol table (these may be identical like in startup, or - different, if you're inside a function).</simpara> - <para> - The following examples use 'active_symbol_table'. You should - replace it with &symbol_table if you specifically want to work - with the 'main' symbol table. Also, the same functions may be - applied to arrays, as explained below.</para> +PHP 3.0ì ì¬ë³¼ í ì´ë¸ì hash í ì´ë¸ì²ë¼ ì ê³µëë¤. +주ì´ì§ ì´ë¤ ìê°ì &symbol_table ì 'main' ì¬ë³¼ í ì´ë¸ì ê°ë¥´í¤ê³ , +active_symbol_tableì íì¬ ì¤íì¤ì¸ ì¬ë³¼ í ì´ë¸ì ê°ë¥´í¨ë¤. +(ì´ê²ìì ìë§ í¨ìë´ìì ì²ìëë ë¤ë¥¸ëìë ëì¼í ê²ì´ë¤.) +</simpara> <para> + +ë¤ìì 'active_symbol_table'ì ì´ì©í ìì ë¤ì´ë¤. ë¹ì ì´ ëª ííê² 'main' ì¬ë³¼ í ì´ë¸ë¡ ìì í길 ìíë©´ &symbol_tableì¼ë¡ ê·¸ê²ì ëì²´í´ì¼ íë¤. +ë§ì°¬ê°ì§ë¡ ê°ì í¨ìë¤ë ë°°ì´ë ìëì ë°í ê²ì²ë¼ ì ì©ë ê²ì´ë¤. +</para> + <para> <example> - <title>Checking whether $foo exists in a symbol table</title> + <title>ì¬ë³¼í ì´ë¸ë´ $fooê° ì¡´ì¬íëì§ ì²´í¬</title> <programlisting> if (hash_exists(active_symbol_table,"foo",sizeof("foo"))) { exists... } else { doesn't exist } </programlisting> </example> <example> - <title>Finding a variable's size in a symbol table</title> + <title>ì¬ë³¼í ì´ë¸ë´ ë³ìíì í¬ê¸° 찾기</title> <programlisting> hash_find(active_symbol_table,"foo",sizeof("foo"),&pvalue); check(pvalue.type); </programlisting> </example> - - Arrays in PHP 3.0 are implemented using the same hashtables as - symbol tables. This means the two above functions can also be - used to check variables inside arrays.</para> +PHP 3.0ì ë°°ì´ì ì¬ë³¼ í ì´ë¸ì²ë¼ ê°ì í´ìí ì´ë¸ë¡ ì¬ì©íë ê²ì ì ê³µëë¤. +ëê° ì´ìì í¨ìê° ë°°ì´ë´ìì ë³ìíì ì²´í¬íë ê²ì í ì ìë¤ë ë»ì´ë¤. +</para> <simpara> - If you want to define a new array in a symbol table, you should do - the following.</simpara> +ë§ì½ ë¹ì ì¬ë³¼í ì´ë¸ë¤ìì ìë¡ì´ ë°°ì´ì ì ìí길 ìíë©´, ë¤ìê³¼ ê°ì´ í´ì¼ íë¤. +</simpara> <simpara> - First, you may want to check whether it exists and abort - appropiately, using hash_exists() or hash_find().</simpara> + 먼ì ë¹ì ì ì²´í¬í길 ìíë ê²ì´ ì¡´ì¬íë ì§ ì¹ì¸ì´ ì·¨ìëìëì§ hash_exists()ë hash_find()ë¡ íì¸í´ì¼ íë¤. +</simpara> <simpara> - Next, initialize the array:</simpara> +ë¤ì, ë°°ì´ì ì´ê¸°ííë¤:</simpara> <para> <example> - <title>Initializing a new array</title> + <title>ì ë°°ì´ ì´ê¸°í</title> <programlisting> pval arr; @@ -260,14 +246,14 @@ hash_update(active_symbol_table,"foo",sizeof("foo"),&arr,sizeof(pval),NULL); </programlisting> </example> - - This code declares a new array, named $foo, in the active symbol - table. This array is empty.</para> +ì´ ì½ëë íì±íë ì¬ë³¼ í ì´ë¸ë´ìì $fooë ì´ë¦ì¼ë¡ ì ë°°ì´ë¡ ì ì¸ëìë¤. +ì´ ë°°ì´ì ë¹ì´ ìë¤.</para> <simpara> - Here's how to add new entries to it:</simpara> +ì¬ê¸°ë ì ìí¸ë¦¬ì ì¶ê°íë ë²ì´ë¤: +</simpara> <para> <example> - <title>Adding entries to a new array</title> + <title>ì ë°°ì´ì ìí¸ë¦¬ ì¶ê°</title> <programlisting> pval entry; @@ -286,34 +272,31 @@ hash_next_index_insert(arr.value.ht,&entry,sizeof(pval),NULL); </programlisting> </example> - - If you'd like to modify a value that you inserted to a hash, you - must first retrieve it from the hash. To prevent that overhead, - you can supply a pval ** to the hash add function, and it'll be - updated with the pval * address of the inserted element inside the - hash. If that value is NULL (like in all of the above examples) - - that parameter is ignored.</para> +ë§ì½ ë¹ì ì´ ë¹ì ì´ hashì ì½ì í ê°ì ë°ê¾¸ê³ ì¶ë¤ë©´ ë¹ì ì 먼ì hashìì ê·¸ê²ì ë°íí´ìì¼ íë¤. + +To prevent that overhead, +ë¹ì ì pval ** ìì hash ì¶ê° í¨ìì ê³µê¸í ì ìê³ , 그건 hashììì ì¶ê°ë ìììpval * 주ìë¡ ìì ë ì ìë¤. +ë§ì½ ê·¸ ê°ì´ NULL (모ë ìì ê° ìë ê²ì²ë¼)ì´ë©´, ê·¸ ì¸ìë 무ìëë¤. +</para> <simpara> - hash_next_index_insert() uses more or less the same logic as - "$foo[] = bar;" in PHP 2.0.</simpara> +PHP 2.0ìì hash_next_index_insert() "$foo[] = bar;"ê°ì ëì¼í ë¡ì§ì¼ë¡ ì¬ì©ëìë¤.</simpara> <simpara> - If you are building an array to return from a function, you can - initialize the array just like above by doing:</simpara> +ë§ì½ í¨ìë¡ë¶í° ë°íì ìí ë°°ì´ì ë§ë ë¤ë©´, ë¤ìê³¼ ê°ì´ ë°°ì´ì ì´ê¸°íí ì ìë¤: +</simpara> <programlisting> if (array_init(return_value) == FAILURE) { failed...; } </programlisting> <simpara> - ...and then adding values with the helper functions:</simpara> +..ê·¸ë¦¬ê³ helperí¨ìì í¨ê» ê°ì ì¶ê°íë¤ +</simpara> <programlisting> add_next_index_long(return_value,long_value); add_next_index_double(return_value,double_value); add_next_index_string(return_value,estrdup(string_value)); </programlisting> <para> - Of course, if the adding isn't done right after the array - initialization, you'd probably have to look for the array first: - - <programlisting> +ë¬¼ë¡ , ë°°ì´ì´ê¸°íí ì¶ê°íì§ ìê² ë¤ë©´, ë°°ì´ì 먼ì ì°¾ìì¼ íë¤: +<programlisting> pval *arr; if (hash_find(active_symbol_table,"foo",sizeof("foo"),(void **)&arr)==FAILURE) { can't find... } @@ -321,18 +304,19 @@ </programlisting> </para> <simpara> - Note that hash_find receives a pointer to a pval pointer, and not - a pval pointer.</simpara> +hash_findë í¬ì¸í°ìì pvalí¬ì¸í°ì pvalí¬ì¸í° ìëì´ë ë°ëë¤. +</simpara> <simpara> - Just about any hash function returns SUCCESS or FAILURE (except - for hash_exists(), which returns a boolean truth value).</simpara> +ê±°ì 모ë hash í¨ìë SUCCESSë FAILUREë§ ë°ííë¤. (ë¶ë¦° íì¤ê°ì ë°ííë hast_exists()ë ì ì¸íë¤). +</simpara> </sect2> <sect2 id="phpdevel-addfunc-retsimple"> - <title>Returning simple values</title> + <title>ê°ë¨í ê° ë°í</title> <simpara> - A number of macros are available to make returning values from a - function easier.</simpara> +매í¬ë¡ì ì«ìì í¨ìë¡ë¶í° ê°ë¨íê² ë¦¬í´ë°ëê² ê°ë¥íë¤. +</simpara> <para> +RETURN_* 매í¬ë¡ë¤ 모ë ë°íê°ê³¼ í¨ììì ë°íëë ëë ê²ì ì íë¤. The RETURN_* macros all set the return value and return from the function: <itemizedlist> @@ -360,7 +344,7 @@ </itemizedlist> </para> <para> - The RETVAL_* macros set the return value, but do not return. +RETVAL_* 매í¬ë¡ë 리í´ê°ì ì¤ì í ì ìì¼ë, ë°íì ëì§ ìëë¤. <itemizedlist> <listitem> <simpara>RETVAL_FALSE</simpara> @@ -383,36 +367,36 @@ </itemizedlist> </para> <simpara> - The string macros above will all estrdup() the passed 's' - argument, so you can safely free the argument after calling the - macro, or alternatively use statically allocated memory.</simpara> +문ìì´ ì¤í¸ë§ì 's'ì¸ìê° íµê³¼ë 모ë estrdup() ì´ìì¼ ê²ì´ë¤. +ê·¸ë¦¬ê³ , ë¹ì ìì íê² ë¶ë¥¸ 매í¬ë¡ë¥¼ ë¶ë¥¸í ì¸ì를 í´ì 를 í ì ìê±°ë, ë¶ê°ì ì¼ë¡ë +ì§ì ë ë©ëª¨ë¦¬ë¥¼ ì ì ì¼ë¡ ì¬ì©í ì ìë¤. +</simpara> <simpara> - If your function returns boolean success/error responses, always - use RETURN_TRUE and RETURN_FALSE respectively.</simpara> +ë§ì½ ë°íë ë¹ì ì í¨ìê° ì°¸/ê±°ì§ ë¶ë¦° ê°ì ë°ííë©´, ê°ê° RETURN_TRUEì RETURN_FALSE ì¸ì ë ì¬ì©íë¤. +</simpara> </sect2> <sect2 id="phpdevel-addfunc-retcomplex"> - <title>Returning complex values</title> + <title>ìì í ê° ë°í</title> <simpara> - Your function can also return a complex data type such as an - object or an array.</simpara> +ë¹ì ì í¨ìë ì´ë¯¸ ê°ì²´ë ë°°ì´ì ìì í ë°ì´í íì ì 리í´í ì ìë¤. +</simpara> <para> - Returning an object: +ê°ì²´ ë°í: <orderedlist numeration="arabic"> <listitem> - <simpara>Call object_init(return_value).</simpara> + <simpara>object_init(return_value)를 ë¶ë¥¸ë¤.</simpara> </listitem> <listitem> - <para>Fill it up with values. The functions available - for this purpose are listed below.</para> + <para>ê°ì¼ë¡ ì±ì´ë¤. 모ë í¨ìë ìëë¡ ì¶ë ¥ëë ê²°ê³¼ê° ê°ë¥íë¤.</para> </listitem> <listitem> - <para> Possibly, register functions for this object. - In order to obtain values from the object, the function would - have to fetch "this" from the active_symbol_table. Its type - should be IS_OBJECT, and it's basically a regular hash table - (i.e., you can use regular hash functions on .value.ht). The - actual registration of the function can be done using: + <para> +ê°ë¥íë¤ë©´ ì´ ê°ì²´ë¥¼ ìí í¨ìë ë±ë¡ìí¨ë¤. +ê°ì²´ë¡ë¶í° ê°ì ì°¨ë¡ëë¡ í¬í¨íê³ , í¨ìë activ_symbol_tableë¡ë¶í° "this"를 ê°ì§ê³ ìì¼ í ê²ì´ë¤. +ì´ë¤ íì ì IS_OBJECTì´ ìëë©´ ìëê³ , 기본ì ì¼ë¡ ì ê· í´ì í ì´ë¸ì´ì´ì¼ íë¤ +(ì, ë¹ì ì .value.htì²ë¼ ì ê· í´ì í¨ì를 ì¬ì©í ì ìë¤) +í¨ìì ì¤ì ë±ë¡ì ë¤ìê³¼ ê°ì´ í ì ìë¤: <programlisting> add_method( return_value, function_name, function_ptr ); </programlisting> @@ -425,42 +409,43 @@ <itemizedlist> <listitem> <simpara>add_property_long( return_value, - property_name, l ) - Add a property named 'property_name', of - type long, equal to 'l'</simpara> + property_name, l ) - longíì , Iì ëì¼í 'property_name'ì´ë¼ë íë¡í¼í° ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_property_double( return_value, - property_name, d ) - Same, only adds a double</simpara> + property_name, d ) - ëªê°ì doubleíì ë§ ì¶ê°</simpara> </listitem> <listitem> <simpara>add_property_string( return_value, - property_name, str ) - Same, only adds a string</simpara> + property_name, str ) - ëªê°ì stringíì ë§ ì¶ê°</simpara> </listitem> <listitem> <simpara>add_property_stringl( return_value, - property_name, str, l ) - Same, only adds a string of length 'l'</simpara> + property_name, str, l ) - ëªê°ì 'l'길ì´ì ì¤í¸ë§ë§ ì¶ê°'</simpara> </listitem> </itemizedlist> </para> <para> - Returning an array: +ë°°ì´ ë°í: <orderedlist numeration="arabic"> <listitem> - <simpara>Call array_init(return_value).</simpara> + <simpara>array_init ë¶ë¥´ê¸°(return_value).</simpara> </listitem> <listitem> - <simpara>Fill it up with values. The functions available - for this purpose are listed below.</simpara> + <simpara>ê°ì¼ë¡ ì±ì°ê¸°. í¨ìë ìë 목ë¡ì ì¬ì©ì ê°ë¥íê² íë¤.</simpara> </listitem> </orderedlist> </para> <para> + The functions used to populate an array are: <itemizedlist> <listitem> - <simpara>add_assoc_long(return_value,key,l) - add - associative entry with key 'key' and long value 'l'</simpara> + <simpara>add_assoc_long(return_value,key,l) - +'ken'í¤ì 'I'ì longì¼ë¡ ë ê³µë ìí¸ë¦¬ +</simpara> </listitem> <listitem> <simpara>add_assoc_double(return_value,key,d)</simpara> @@ -470,11 +455,13 @@ </listitem> <listitem> <simpara>add_assoc_stringl(return_value,key,str,length,duplicate) - specify the string length</simpara> +ì¤í¸ë§ ê¸¸ì´ ì§ì +</simpara> </listitem> <listitem> - <simpara>add_index_long(return_value,index,l) - add - entry in index 'index' with long value 'l'</simpara> + <simpara>add_index_long(return_value,index,l) - +ìí¸ë¦¬ì 'index' ì¸ë±ì¤ì 'i'ì¼ë¡ ë longì ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_index_double(return_value,index,d)</simpara> @@ -484,11 +471,12 @@ </listitem> <listitem> <simpara>add_index_stringl(return_value,index,str,length) - - specify the string length</simpara> + - 문ìì´ ê¸¸ì´ ì§ì </simpara> </listitem> <listitem> - <simpara>add_next_index_long(return_value,l) - add an - array entry in the next free offset with long value 'l'</simpara> + <simpara>add_next_index_long(return_value,l) - +ë°°ì´ ìí¸ë¦¬ì 'ã £'ì¼ë¡ ë longì ë¤ì free offsetì ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_next_index_double(return_value,d)</simpara> @@ -498,18 +486,17 @@ </listitem> <listitem> <simpara>add_next_index_stringl(return_value,str,length) - - specify the string length</simpara> + - 문ìì´ ê¸¸ì´ ì§ì </simpara> </listitem> </itemizedlist> </para> </sect2> <sect2 id="phpdevel-addfunc-reslist"> - <title>Using the resource list</title> + <title>ìì ëª©ë¡ ì¬ì©í기</title> <simpara> - PHP 3.0 has a standard way of dealing with various types of - resources. This replaces all of the local linked lists in PHP 2.0.</simpara> + PHP 3.0ì ì¬ë¬ ììì ê°ì§ íí를 ë¤ë£¨ë íì¤ì ì¸ ë°©ë²ì ê°ì§ê³ ìë¤. ì´ê²ì PHP 2.0ì 모ë ì§ìì ì¸ linked list를 ëì²´íë¤</simpara> <para> - Available functions: +ê°ë¥í í¨ì: <itemizedlist> <listitem> @@ -581,11 +568,7 @@ <sect2 id="phpdevel-addfunc-prestable"> <title>Using the persistent resource table</title> <para> - PHP 3.0 has a standard way of storing persistent resources (i.e., - resources that are kept in between hits). The first module to use - this feature was the MySQL module, and mSQL followed it, so one - can get the general impression of how a persistent resource should - be used by reading mysql.c. The functions you should look at are: + PHP 3.0ì ì구ì ì¸ ìì(persistent resources; ì, ê·¸ëìì íí¸ì를 ë³´ê´íë ìì)ì ì ì¥íë íì¤ì ì¸ ë°©ë²ì ê°ì§ê³ ìë¤. ì´ ë°©ë²ì MySQL 모ëìì ì²ìì¬ì©ëìê³ , mSQLë ì´ê²ì ë°ë¥´ê³ ìë¤. ë°ë¼ì persistent resource를 ì´ë»ê² ì¬ì©íëê°ì ëí´ ìê³ ì¶ë¤ë©´ ì°ì mysql.c를 ì½ì´ë³´ëë¡íì. 주ìí´ì ë³¼ í¨ìë¤ì ë¤ìê³¼ ê°ë¤: <simplelist> <member>php3_mysql_do_connect</member> @@ -594,7 +577,7 @@ </simplelist> </para> <para> - The general idea of persistence modules is this: +persistence 모ëì ì¼ë°ì ì¸ ideaë ë¤ìê³¼ ê°ë¤: <orderedlist numeration="arabic"> <listitem> <simpara>Code all of your module to work with the @@ -677,17 +660,9 @@ mustn't use efree() here either.</simpara> </sect2> <sect2 id="phpdevel-addfunc-addcfg"> - <title>Adding runtime configuration directives</title> + <title>ë°íì ì¤ì ì§ìì(directives) ì¶ê°</title> <para> - Many of the features of PHP 3 can be configured at runtime. These - configuration directives can appear in either the designated - php3.ini file, or in the case of the Apache module version in the - Apache .conf files. The advantage of having them in the Apache - .conf files is that they can be configured on a per-directory - basis. This means that one directory may have a certain - safemodeexecdir for example, while another directory may have - another. This configuration granularity is especially handy when - a server supports multiple virtual hosts.</para> + ë§ì PHPì 기ë¥(feature)ë¤ì´ ì¤íì¤ì ì¤ì ê°ë¥íë¤. ì´ ì¤ì ì§ìì(configuration directives)ë php3.iniì ì¤ì ëê±°ë, Apache 모ëì ê²½ì° .conf íì¼ì ì¤ì ê°ë¥íëë¡ ëì´ ìë¤. Apache .conf íì¼ì ì¤ì íë ê²ì ì¥ì ì ëë í 리ë³ë¡ ì¤ì ì ë¤ë¥´ê² í ì ìë¤ë ì ì´ë¤. ì´ê²ì ì를ë¤ì´ ì´ë¤ ëë í ë¦¬ê° ë¤ë¥¸ ëë í 리를 ê°ì§ê³ ìì´ë, í´ë¹íë í ëë í 리ìë§ safemodeexecdir ì¤ì ì í ì ìë¤ë ê²ì´ë¤. ì´ ê°ë³ ì¤ì 기ë¥ì ìë²ê° multiple virtual hosts를 ì§ìí ë ë¬´ì² ì ì©íë¤</para> <para> The steps required to add a new directive: @@ -727,10 +702,9 @@ </sect2> </sect1> <sect1 id="calling-user-functions"> - <title>Calling User Functions</title> + <title>ì¬ì©ì í¨ì를 ë¶ë¥´ê¸°</title> <simpara> - To call user functions from an internal function, you should use - the <function>call_user_function</function> function. +ë´ë¶ í¨ì(internal function)ìì ì¬ì©ì í¨ì를 ë¶ë¥´ë ¤ë©´, <function>call_user_function</function>í¨ì를 ì¬ì©íì¬ì¼ íë¤. </simpara> <simpara> <function>call_user_function</function> returns SUCCESS on success, @@ -806,98 +780,73 @@ <sect1 id="phpdevel-errors"> <title>Reporting Errors</title> <simpara> - To report errors from an internal function, you should call the - <function>php3_error</function> function. This takes at least two - parameters -- the first is the level of the error, the second is - the format string for the error message (as in a standard - <function>printf</function> call), and any following arguments - are the parameters for the format string. The error levels are: - </simpara> +ë´ë¶ í¨ììì ìë¬ë¥¼ reportí ëë <function>php3_error</function>í¨ì를 ì¬ì©íë ê²ì´ ì¢ë¤. ì´ í¨ìë ìµì ëê°ì ì¸ì를 ê°ì§ê³ í¸ì¶ëë¤. 첫ë²ì§¸ë ìë¬ì levelì´ê³ , ë¤ë¥¸ íëë ìë¬ ë©ì¸ì§ë¥¼ ìí format string( <function>printf</function>ìì ì¬ì©ëë ê²ê³¼ ê°ì íí) ì´ë¤. ê·¸ë¦¬ê³ ê·¸ ë머ì§ë 주ì´ì§ format stringì parameterê° ëë¤. ìë¬ levelì ë¤ìê³¼ ê°ë¤: </simpara> <sect2 id="internal.e-notice"> <title>E_NOTICE</title> <simpara> - Notices are not printed by default, and indicate that the script - encountered something that could indicate an error, but could also - happen in the normal course of running a script. For example, - trying to access the value of a variable which has not been set, - or calling <function>stat</function> on a file that doesn't exist. +Noticeë 기본ì ì¼ë¡ë ì¶ë ¥ëì§ ìëë¤. ì´ê²ì ì¤í¬ë¦½í¸ê° ëê° ìë¬ë¥¼ ê°ì§íì§ë§, ê·¸ê²ì´ ì ìì ì¸ ìí©ìì ë°ìíë ê²ì´ë¼ë ì미ì´ë¤. ì를ë¤ì´ ì¤ì ëì§ ìì ë³ì를 ì¬ì©íë ¤ íê±°ë, ì¡´ì¬íì§ ìë íì¼ì <function>stat</function>í¨ì를 í¸ì¶íë ê² ë±ì´ë¤. </simpara> </sect2> <sect2 id="internal.e-warning"> <title>E_WARNING</title> <simpara> - Warnings are printed by default, but do not interrupt script - execution. These indicate a problem that should have been trapped - by the script before the call was made. For example, calling - <function>ereg</function> with an invalid regular expression. +Warningì 기본ì ì¼ë¡ ì¶ë ¥ëë¤. ê·¸ë¬ë, ì¤í¬ë¦½í¸ì ì¤íì ë©ì¶ì§ë ìëë¤. ì´ê²ì í¸ì¶ì´ ìë£ë기 ì ì ì¤í¬ë¦½í¸ì ìí´ ì¡íì ¸ì¼ íë 문ì 를 ê°ë¦¬í¨ë¤. ì를ë¤ì´ ì못ë regular expressionì¼ë¡ <function>ereg</function>를 í¸ì¶íë ê² ë±ì´ë¤. </simpara> </sect2> <sect2 id="internal.e-error"> <title>E_ERROR</title> <simpara> - Errors are also printed by default, and execution of the script is - halted after the function returns. These indicate errors that can - not be recovered from, such as a memory allocation problem. - </simpara> +Errorë 기본ì ì¼ë¡ ì¶ë ¥ëë¤. ê·¸ë¦¬ê³ , í¨ìì ì¤íì´ ìë£ë ì§í, ì¤í¬ë¦½í¸ì ì¤íì ë©ì¶ë¤. ì´ê²ì memory allocation 문ì ê°ì ë³µêµ¬ê° ë¶ê°ë¥í ìë¬ë¥¼ ì미íë¤ </simpara> </sect2> <sect2 id="internal.e-parse"> <title>E_PARSE</title> <simpara> - Parse errors should only be generated by the parser. The code is - listed here only for the sake of completeness. +Parse errorë ì¤ì§ Parserë§ì´ ìì±ê°ë¥íë¤. codeê° listëë¤. </simpara> </sect2> <sect2 id="internal.e-core-error"> <title>E_CORE_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated by the core - of PHP. Functions should not generate this type of error. - </simpara> +PHPì coreììí´ ìì±ëë¤ë ì ì ì ì¸íê³ ë E_ERRORì ëì¼íë¤. ì¼ë° í¨ìë¡ë ì´ ííì ìë¬ë¥¼ ë§ë¤ì§ 못íë¤. </simpara> </sect2> <sect2 id="internal.e-core-warning"> <title>E_CORE_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by the core - of PHP. Functions should not generate this type of error. - </simpara> +PHPì coreììí´ ìì±ëë¤ë ì ì ì ì¸íê³ ë E_WARNINGì ëì¼íë¤. ì¼ë° í¨ìë¡ë ì´ ííì ìë¬ë¥¼ ë§ë¤ì§ 못íë¤.</simpara> </sect2> <sect2 id="internal.e-compile-error"> <title>E_COMPILE_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated by the Zend Scripting - Engine. Functions should not generate this type of error. +ì´ê²ì E-Errorë ë¹ì·íë¤, ìì¸ì ì¼ë¡ Zendì¤í¬ë¦½í ìì§ì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-compile-warning"> <title>E_COMPILE_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by the Zend Scripting - Engine. Functions should not generate this type of error. - </simpara> +ì´ê²ì E_WARNINGì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ Zend ì¤í¬ë¦½í ìì§ì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. +</simpara> </sect2> <sect2 id="internal.e-user-error"> <title>E_USER_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated in PHP code by using - the PHP function <function>trigger_error</function>. Functions should - not generate this type of error. +ì´ê²ì E_ERRORì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-user-warning"> <title>E_USER_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by using the PHP - function <function>trigger_error</function>. Functions should not - generate this type of error. +ì´ê²ì E_WARNINGì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-user-notice"> <title>E_USER_NOTICE</title> <simpara> - This is like an E_NOTICE, except it is generated by using the PHP - function <function>trigger_error</function>. Functions should not - generate this type of error. - </simpara> +ì´ê²ì E_NOTICEë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤.</simpara> </sect2> </sect1> </appendix> Index: phpdoc/kr/appendices/regexp.xml diff -u phpdoc/kr/appendices/regexp.xml:1.2 phpdoc/kr/appendices/regexp.xml:1.3 --- phpdoc/kr/appendices/regexp.xml:1.2 Tue Jan 9 16:33:39 2001 +++ phpdoc/kr/appendices/regexp.xml Thu Jan 18 21:26:38 2001 @@ -1,3 +1,3 @@ -<chapt>Regular expressions +<chapt>Regular expressions <sect>Short overview to regexps with pointers to more info Index: phpdoc/kr/chapters/intro.xml diff -u phpdoc/kr/chapters/intro.xml:1.2 phpdoc/kr/chapters/intro.xml:1.3 --- phpdoc/kr/chapters/intro.xml:1.2 Sun Jan 7 10:48:41 2001 +++ phpdoc/kr/chapters/intro.xml Thu Jan 18 21:26:39 2001 @@ -1,18 +1,18 @@ - <chapter id="introduction"> - <title>ìê° (Introduction)</title> + <chapter id="introduction"> + <title>?ëì»» (Introduction)</title> <sect1 id="intro-whatis"> - <title>PHPë 무ìì¸ê°?</title> + <title>PHP? è¾ë뾿?멸??</title> <simpara> - PHP(ê³µìì ì¼ë¡ "PHP: Hypertext Preprocessor ")ë server-side - HTML-embedded scripting languageì ëë¤. + PHP(æ¨ëë?ê³¸ìæ¿¡?"PHP: Hypertext Preprocessor ")??server-side + HTML-embedded scripting language?ë ë²?? </simpara> <para> - ê°ë¨í ëµì´ì§ë§, 무ìì ì미í ê¹? ë¤ì ì를 ë³´ì: + åªê¾¨ë???ëì ï§Âï§? è¾ë뾿???ì??ì¢í´? ?ã ¼ì¬ ?ë? è¹ëì: </para> <para> <example> - <title>ìê°ì© ì문</title> + <title>?ëì»»???ëЦ</title> <programlisting role="php"> <html> <head> @@ -30,13 +30,13 @@ </example> </para> <para> - Perlì´ë Cì ê°ì ë¤ë¥¸ CGI ì¤í¬ë¦½í¸ì ë¬ë¦¬ HTMLì ì¶ë ¥íëë° ë§ì ëª ë ¹ì´ê° íììë¤. - ë¹ì ì HTMLë´ì ë¹ì ì´ íê³ ì íë ì¼(ìì ìì° íì¤ì 문ìì´ ì¶ë ¥)ì ëí ì¤í¬ë¦½í¸ë¥¼ ì ì´ì£¼ë©´ ëë¤. - PHPì½ëë í¹ì í <link linkend="language.basic-syntax.phpmode">ììê³¼ ë íê·¸</link> - ì¬ì´ì ë¤ì´ê°ê² ëëë°, ì´ íí¬ë PHP모ëë¡ ë¤ì´ê°ê±°ë ëì¤ë ê²ì´ë¤. + Perl?ëêµ¹ C? åªì? ?㠻⠨ CGI ?ã ½ê²ç±ìë? ?Ñâ HTML??ç°ìì °?ìë??ï§ë¡®? ï§ë ì¡?ë¿? ?꾩ì?ë ¿ë. + ?ë±ë? HTML?ëë¿ ?ë±ë???ìí¬???ìë ???ê¾©ì½ ?ê³¸ì¦ ?ì쨪??è¾ëªì??ç°ìì °)???Â???ã ½ê²ç±ìëç??곸뼱äºì°ã ?ìë. + PHPè붾뱶???ë±ì ??<link linkend="language.basic-syntax.phpmode">?ììæ¨????ìë </link> + ?Ñì ???㠼뼱åªÂå¯??ìë?? ???ìê²??PHPï§â¤ë±¶æ¿¡??㠼뼱åªÂå«ê³êµ¹ ?ìì¤??å¯ê»ì ?? </para> <para> - PHPê° ë¤ë¥¸ Clien-side Javascripì 구ë³ëë ê²ì ì´ ì½ëê° ìë²ìì ì¤íëë¤ë ê²ì´ë¤. + PHPåªÂ ?㠻⠨ Clien-side Javascrip? æ´Ñí?ìë å¯ê»? ??è붾뱶åªÂ ?ìì¾?ë¨¯ê½ ?㠽뻾?ìë??å¯ê»ì ?? If you were to have a script similar to the above on your server, the client would receive the results of running that script, with no way of determining what @@ -47,15 +47,15 @@ </sect1> <sect1 id="intro-whatcando"> - <title>PHPë¡ ë¬´ìì í ì ìëê°?</title> + <title>PHPæ¿¡?è¾ë뾿???????ëëåªÂ?</title> <para> - ê°ì¥ 기본ì ì¸ ë 벨ìì, PHPë ë¤ë¥¸ CGIíë¡ê·¸ë¨ì´ í ì ìë 모ë ê²ì í ì ìë¤. - from data를 ê°ì ¸ì¤ê³ , ëì ì¸ ì¹íì´ì§ë¥¼ ë§ë¤ê±°ë, Cookie를 ë³´ë´ê³ ë°ì ìë ìë¤. + åªÂ??æ¹²ê³ë¯?ê³¸ì¤ ?ë꺼?먯ê½, PHP???㠻⠨ CGI?ê¾¨ì¤æ´¹ëªì©???????ëë ï§â¤ë±º å¯ê»ì£ ?ì¢ë ?ëë. + from dataç?åªÂ?ëªì¤æ¨? ?ìì»???ë±ë¹?ë?ç?ï§ë®ë±¾å«ê³êµ¹, Cookieç?è¹ëê¶¡æ¨?è«ìì£ ?ìë£ ?ëë. </para> <para> - ìë§ PHPì ê°ì¥ ê°ë ¥íê³ ê´ì¬ì´ ê°ë ë¶ë¶ì ë°ì´íë² ì´ì¤ë¤ì íëì ì§ìì´ë¤. - PHP를 ì¬ì©íë©´ ë¹ì ì Database를 ì¬ì©í ì¹íì´ì§ë¥¼ ëëëë¡ ê°ë¨í ë§ë¤ ì ìë¤. - ë¤ìì ì¼ë°ì ì¸ Databaseë¤ì ì§ìíë¤: + ?꾨ì PHP??åªÂ??åªëº£ì °?ìí¬ æ¿Â?Ñì åªÂ??éºÂéºê¾©? ?ê³ì ?Â踰ì¢ì ?㠻뱾????ê¼»? ï§Â?먯ì ?? + PHPç??Ñì?ìã ?ë±ë? Databaseç??Ñì???ë±ë¹?ë?ç??Â?ë¾ë£æ¿¡?åªê¾¨ë??ï§ë®ë±¾ ???ëë. + ?ã ¼ì¬???ì°ì»²?ê³¸ì¤ Database?ã ¼ì£ ï§Â?먰븳?? <blockquote> <simplelist columns="3"> <member>Adabas D</member> @@ -83,9 +83,9 @@ </blockquote> </para> <para> - PHPë IMAP, SNMP, NNTP, POP3, HTTPë±ì íë¡ì½í¨ê³¼ ë ë¤ë¥¸ ê²ë¤ì ì¬ì©íë - ë¤ë¥¸ ìë¹ì¤ë¤ì ëí´ìë ì´ë¯¸ ì§ìíê³ ìë¤. ì¬ì´ì§ë raw network ìì¼ì ì¬ì©íë©´, - ê·¸ì¸ì ë¤ë¥¸ íë¡í ì½ë¤ì ì¬ì©í ìë ìë¤. + PHP??IMAP, SNMP, NNTP, POP3, HTTP?ê¹ì½ ?꾨ì¤èë·ë§æ¨????㠻⠨ å¯ê»ë±¾???Ñì?ìë + ?㠻⠨ ?ìí¬?㠻뱾???Â?ëê½???ë? ï§Â?먰븯æ¨??ëë. ?Ñë¼±ï§Â??raw network ?ë¯í???Ñì?ìã, + æ´¹ëªì ???㠻⠨ ?꾨ì¤?ì¢í³?ã ¼ì£ ?Ñì???ìë£ ?ëë. </para> <!-- <figure> @@ -100,10 +100,10 @@ </sect1> <sect1 id="intro-history"> - <title>PHPì ìì¬</title> + <title>PHP????ê¶</title> <simpara> - PHPë 1994ë ê°ì &link.rasmus;ê° ì²ì ê³ ìíìë¤. - ì´ê¸° ë¹ê³µê°ë²ì ì ê·¸ì ííì´ì§ì ì¬ëê° ëê° ê·¸ì ì¨ë¼ì¸ ì´ë ¥ì를 ë´¤ëì§ ë³´ê´íëë° ì¬ì©ëìë¤. + PHP??1994??åªÂ??&link.rasmus;åªÂ ï§£ìì¬ æ¨ì¢ë¸?ì??? + ç¥ë린 é®ê¾§ë¬åªìì¾?꾩? æ´¹ëªì½ ?ëë¹?ë????Ñë»åªÂ ?ê¾§? æ´¹ëªì½ ?â¤ìª???ëì °?ì? éã »ëï§Â è¹ë¿??ìë???Ñì?ìë¿?? The first version used by others was available sometime in early 1995 and was known as the Personal Home Page Tools. It consisted of a very
Index: phpdoc/kr/appendices/debugger.xml diff -u phpdoc/kr/appendices/debugger.xml:1.3 phpdoc/kr/appendices/debugger.xml:1.4 --- phpdoc/kr/appendices/debugger.xml:1.3 Thu Jan 11 20:10:47 2001 +++ phpdoc/kr/appendices/debugger.xml Thu Jan 18 21:26:38 2001 @@ -1,63 +1,54 @@ <appendix id="debugger"> <title>The PHP Debugger</title> <sect1 id="debugger-using"> - <title>Using the Debugger</title> + <title>ëë²ê±° ì¬ì©ê¸°</title> <para> - PHP's internal debugger is useful for tracking down evasive bugs. - The debugger works by connecting to a <acronym>TCP</acronym> port - for every time PHP starts up. All error messages from that - request will be sent to this TCP connection. This information is - intended for "debugging server" that can run inside an - <acronym>IDE</acronym> or programmable editor (such as Emacs). + PHPì ë´ë¶ ëë²ê±°ë ìììë ë¤ì´ ë²ê·¸ë¤ì ì ì©íë¤. + ì´ ëë²ê±°ë PHPê° ìëíë ëì ë´ë´ <acronym>TCP</acronym> í¬í¸ì ì ìí´ì ìì ëë¤. + ìì²(Request)ë TCPì ìì ë³´ë´ì 모ë ìë¬ ë©ì¸ì§ê° ëì¨ë¤. + <acronym>IDE</acronym>ë Progrmmable ìëí° ììì ì¤íëë "ëë²ê¹ ìë²(Debugging server"ì ê°ì ì ì¸ ì ë³´ì´ë¤(Emacsì²ë¼). + </para> <para> - How to set up the debugger: + ëë²ê±° ì¤ì¹íë ë°©ë²: <orderedlist> <listitem> <simpara> - Set up a TCP port for the debugger in the <link linkend="configuration.file">configuration file</link> (<link linkend="ini.debugger.port">debugger.port</link>) and enable it - (<link linkend="ini.debugger.enabled">debugger.enabled</link>). + ëë²ê±°ë¥¼ ìí TCP í¬í¸ ì¤ì¹ë <link linkend="configuration.file">configuration file</link>ìì ìë¤. + (<link linkend="ini.debugger.port">debugger.port</link>)ê³¼ ê°ë¥ì¤ì (<link linkend="ini.debugger.enabled">debugger.enabled</link>) </simpara> </listitem> <listitem> <simpara> - Set up a TCP listener on that port somewhere (for example + ì´ëê°ì í¬í¸ìì TCP ê°ìì(lestener) ì¤ì¹ (ì를 ë¤ì´ <command>socket -l -s 1400</command> on UNIX). </simpara> </listitem> <listitem> <simpara> - In your code, run - "debugger_on(<replaceable>host</replaceable>)", where - <replaceable>host</replaceable> is the IP number or name of the - host running the <acronym>TCP</acronym> listener. +ë¹ì ì ì½ëìì íê³ , +<acronym>TCP</acronym> ê°ìì(listener)ê° ì¤í´ëë ëì <replaceable>host</replaceable>ë IP ì«ìì í¸ì¤í¸ì ì´ë¦ì ê°ì§ <replaceable>host</replaceable>ìì "debugger_on(<replaceable>host</replaceable>)"ì ì¤í. </simpara> </listitem> </orderedlist> - Now, all warnings, notices etc. will show up on that listener - socket, <emphasis>even if you them turned off with - <function>error_reporting</function> - </emphasis>. + 모ë ê²½ê³ ë ê°ìì ìì¼(listener socket)ë ê³µì§ëë¤. + <emphasis>ë¹ë¡ <function>error_reporting</function>ì ìí´ êº¼ì ¸ìëë¼ë</emphasis>. </para> <note> <para> - The code for the debugger has not been ported to PHP 4, at the - present time only PHP 3 supports the debugger code. - </para> + ëë²ê±°ë¥¼ ìí ì½ë PHP4ììë ì ê³µëì§ ìëë¤. ì´ê²ì PHP3ììë§ ì ê³µëë¤. + </para> </note> </sect1> <sect1 id="debugger-protocol"> - <title>Debugger Protocol</title> + <title>ëë²ê±° íë¡í ì½(Debugger Protocl)</title> <para> - The debugger protocol is line-based. Each line has a - <emphasis>type</emphasis>, and several lines compose a - <emphasis>message</emphasis>. Each message starts with a line of - the type <literal>start</literal> and terminates with a line of - the type <literal>end</literal>. PHP may send lines for different - messages simultaneously. + ëë²ê±° íë¡ì½í¨ì ë¼ì¸ 기ë°ì´ë¤. ê° ë¼ì¸ì <emphasis>type</emphasis>ê³¼ <emphasis>message</emphasis>ë¡ ì´ë£¨ì´ì§ ëªëª ë¼ì¸ë¤ì ê°ì§ë¤. + ê° ë©ì¸ì§ë <literal>start</literal>íì ì ë¼ì¸ì¼ë¡ ììëê³ , <literal>end</literal>íì ì ë¼ì¸ì¼ë¡ ìí´ ì¤ì§ëë¤. + PHPë ìë§ ì¼ì í ë¤ë¥¸ ë©ì¸ì§ë¤ì ë¼ì¸ë¤ì ë³´ë¼ê²ì´ë¤. </para> <para> - A line has this format: +ê° ë¼ì¸ì ë¤ìì í¬ë§·ì ê°ì§ë¤: <informalexample> <literallayout> <replaceable>date</replaceable> Index: phpdoc/kr/appendices/phpdevel.xml diff -u phpdoc/kr/appendices/phpdevel.xml:1.3 phpdoc/kr/appendices/phpdevel.xml:1.4 --- phpdoc/kr/appendices/phpdevel.xml:1.3 Thu Jan 11 20:10:47 2001 +++ phpdoc/kr/appendices/phpdevel.xml Thu Jan 18 21:26:38 2001 @@ -18,14 +18,12 @@ <sect2 id="phpdevel-addfunc-args"> <title>í¨ì ì¸ì</title> <para> - - Arguments are always of type pval. This type contains a union - which has the actual type of the argument. So, if your function - takes two arguments, you would do something like the following at - the top of your function:</para> +ì¸ìë ì¸ì ë pvalíì ì´ë¤. ì´ íì ì ì¸ìì ì¤ì íì (actual type)ì ê²°í©ì í¬í¨íë¤. +ê·¸ëì, ë¹ì ì í¨ìê° 2ê°ì ì¸ì를 ê°ì§ë¤ë©´ ë¹ì ì ë¹ì ì í¨ì 맨ììì ë°ë¥´ëê²ì²ë¼ í´ì¼ í ê²ì´ë¤: +</para> <para> <example> - <title>Fetching function arguments</title> + <title>í¨ì ì¸ì ê°ì ¸ì¤ê¸°</title> <programlisting> pval *arg1, *arg2; if (ARG_COUNT(ht) != 2 || getParameters(ht,2,&arg1,&arg2)==FAILURE) { @@ -33,33 +31,32 @@ } </programlisting> </example> - - NOTE: Arguments can be passed either by value or by reference. In - both cases you will need to pass &(pval *) to getParameters. If - you want to check if the n'th parameter was sent to you by - reference or not, you can use the function, - ParameterPassedByReference(ht,n). It will return either 1 or 0.</para> - <simpara> - When you change any of the passed parameters, whether they are - sent by reference or by value, you can either start over with the - parameter by calling pval_destructor on it, or if it's an ARRAY - you want to add to, you can use functions similar to the ones in - internal_functions.h which manipulate return_value as an ARRAY.</simpara> - <simpara> - Also if you change a parameter to IS_STRING make sure you first - assign the new estrdup()'ed string and the string length, and only - later change the type to IS_STRING. If you change the string of a - parameter which already IS_STRING or IS_ARRAY you should run - pval_destructor on it first.</simpara> +ë ¸í¸ : í¨ìë ê°ì´ë 참조 ëì¤ íëë¡ ì¸ì를 ë길ì ìë¤. +ì쪽 ê²½ì°ë¤ ë¹ì ì &(pval *) ìì getParametersë¡ íµê³¼íëê² íìí ê²ì´ë¤. +ë¹ì ì´ ì²´í¬íê² ë¤ë©´ ëªë²ì§¸ ì¸ìê° ë¹ì ìê² ì°¸ì¡°ê°ì´ë ìëê²ì¼ë¡ ë³´ë´ì§ëì§ +ìë¤ë©´ í¨ììì ì¬ì©í ì ìë¤. +ParameterPassedByReference(ht,n). 그건 1ì´ë 0 ê°ì ë°ííë¤. +</para> + <simpara> +ë¹ì ì ëê²¨ì¨ ì¸ìì ì´ë¤ê²ì ë³ê²½í ë ê·¸ë¤ì 참조ë ê°ì ìí´ ë³´ë¼ì§ ìëì§ +pval_destuctor ë¼ ë¶ë¦¬ì´ ì¸ì를 ììíê±°ë, ë§ì½ ë°°ì´ì´ë¼ë©´ ì¶ê°í ë í¨ì ë¹ì«íê² +ë°°ì´ê°ì ë°íê°ì ë¤ë£¨ë internal_functions.hë´ìì ì¬ì©í ì ìë¤ +</simpara> + <simpara> +ì´ë¯¸ ë¹ì ì IS_STRINGì¼ë¡ ì¸ì를 ë°ê¾¼ë¤ë©´ ìë¡ì´ estrdup()ìë 문ìì´, 문ìì´ ê¸¸ì´, +ê°ì¥ ëì¤ì ë°ê¾¼ IS_STRINGì íì ì 먼ì í ë¹íë ê²ì íì¤í í´ì¼ íë¤. +ì´ë¯¸ ì¡´ì¬íë IS_STRINGì´ë IS_ARRAYê°ì ì¸ìì 문ìì´ì ë°ê¾¼ë¤ë©´ +pval_destructor를 먼ì ì¤íí´ì¼ í ê²ì´ë¤.</simpara> </sect2> <sect2 id="phpdevel-addfunc-varargs"> - <title>Variable Function Arguments</title> + <title>ë³ìí í¨ì í본</title> <para> - A function can take a variable number of arguments. If your function can - take either 2 or 3 arguments, use the following:</para> +ì´ í¨ìë í본ì ë³ìí ì«ì ê°ì§ ì ìë¤. +ë¹ì ì í¨ìê° 2ê°ë 3ê°ì ì¸ì를 ê°ì§ì ìë¤ë©´ ë¤ìê³¼ ê°ì´ ì¬ì©íë¼: +</para> <para> <example> - <title>Variable function arguments</title> + <title>ë³ìí í¨ì ì¸ì</title> <programlisting> pval *arg1, *arg2, *arg3; int arg_count = ARG_COUNT(ht); @@ -73,13 +70,11 @@ </para> </sect2> <sect2 id="phpdevel-addfunc-using-args"> - <title>Using the Function Arguments</title> + <title>í¨ì ì¸ì ì¬ì©í기</title> <para> - The type of each argument is stored in the pval type field. This - type can be any of the following: - +ê° ì¸ìì íì ì pvalíì íëë¡ ì ì¥ëë¤. ì´ íì ì ë¤ìì¤ ì´ëê²ì´ë ì¬ì©í ì ìë¤: <table> - <title>PHP Internal Types</title> + <title>PHP ë´ë¶ íì ë¤</title> <tgroup cols="2"> <tbody> <row> @@ -123,11 +118,9 @@ </table> </para> <para> - If you get an argument of one type and would like to use it as - another, or if you just want to force the argument to be of a - certain type, you can use one of the following conversion - functions: - +ë¹ì ì´ íëì íì ì¸ì ê°ì§ë ê²ê³¼ ë¤ë¥¸ ê²ì²ë¼ ì¬ì©í길 ë°ë¼ë ê² ëë +ë¨ì§ íì¤í íì ì ì¸ì를 ìíí길 ìíë¤ë©´, +ë¹ì ì ì íí¨ìë¤ ì¤ íë를 ì¸ì ìë¤: <programlisting> convert_to_long(arg1); convert_to_double(arg1); @@ -137,9 +130,9 @@ </programlisting> </para> <simpara> - These function all do in-place conversion. They do not return anything.</simpara> +ì´ë¤ í¨ìë 모ë íëë¡ ë³í를 íë¤. ìë¬´ë° ë°íì íì§ ìëë¤.</simpara> <para> - The actual argument is stored in a union; the members are: +ì¤ì ì ì¸ ì¸ìë ê²°í©ì²´ë¡ ì ì¥ëë¤; ê·¸ 구ì±ìì: <itemizedlist> <listitem> <simpara>IS_STRING: arg1->value.str.val</simpara> @@ -154,26 +147,23 @@ </para> </sect2> <sect2 id="phpdevel-addfunc-memmgmt"> - <title>Memory Management in Functions</title> + <title>í¨ìë´ ë©ëª¨ë¦¬ ê´ë¦¬</title> + <simpara> +모ë ë©ëª¨ë¦¬ë emalloc()ì´ë estrdup()ë¡ í ë¹ëë í¨ìê° íìíë¤. +ì´ê²ë¤ì malloc()ì strdup()í¨ìê³¼ ê°ì´ ë³´ì´ë ë©ëª¨ë¦¬ì²ë¦¬ê°ìí¨ìì´ë¤. +ë©ëª¨ë¦¬ë efree()ë¡ í´ì ë ì ìë¤. +</simpara> + <simpara> +ì´ íë¡ê·¸ë¨ë´ìì ë ì¢ ë¥ì ë©ëª¨ë¦¬ë: +ë³ìíìì íì를 ë°ííë ê²ê³¼ ë¹ì ì´ ë´ë¶ í¨ìë´ íìí ìì 기ìµì¥ì. +ë¹ì ì´ ë¬¸ìì´ì ë³ìíì¼ë¡ ì§ì í ë +ë°íë íìê° emalloc()ë estrdup()ì 먼ì ë©ëª¨ë¦¬ì í ë¹ëìëì§ íì¸í´ì¼ íë¤. +</simpara> <simpara> - Any memory needed by a function should be allocated with either - emalloc() or estrdup(). These are memory handling abstraction - functions that look and smell like the normal malloc() and - strdup() functions. Memory should be freed with efree().</simpara> - <simpara> - There are two kinds of memory in this program: memory which is - returned to the parser in a variable, and memory which you need for - temporary storage in your internal function. When you assign a - string to a variable which is returned to the parser you need to - make sure you first allocate the memory with either emalloc() or - estrdup(). This memory should NEVER be freed by you, unless you - later in the same function overwrite your original assignment - (this kind of programming practice is not good though).</simpara> - <simpara> - For any temporary/permanent memory you need in your - functions/library you should use the three emalloc(), estrdup(), - and efree() functions. They behave EXACTLY like their counterpart - functions. Anything you emalloc() or estrdup() you have to efree() +ì´ë¤ ìì/ ì구 ë©ëª¨ë¦¬ë¥¼ ìí´ ë¹ì ì ë¹ì ì í¨ì/ë¼ì´ë¸ë¬ë¦¬ë´ìì emalloc(), estrdup(), ê·¸ë¦¬ê³ efree() í¨ì 3ê°ë¥¼ ì´ì©í´ì¼ íë¤. +ë¹ì ì ì¬ë³¸ í¨ìì²ë¼ ì íí í´ì¼ í ê²ì´ë¤. + + Anything you emalloc() or estrdup() you have to efree() at some point or another, unless it's supposed to stick around until the end of the program; otherwise, there will be a memory leak. The meaning of "the functions behave exactly like their @@ -181,16 +171,13 @@ emalloc()'ed nor estrdup()'ed you might get a segmentation fault. So please take care and free all of your wasted memory.</simpara> <simpara> - If you compile with "-DDEBUG", PHP 3 will print out a list of all - memory that was allocated using emalloc() and estrdup() but never - freed with efree() when it is done running the specified script.</simpara> +ë§ì½ ë¹ì ì´ "-DDEBUG"ë¡ ì»´íì¼íë¤ë©´ PHP3ë ì§ì ë emalloc()ê³¼ estrdup() ì¬ì©í 모ë ë©ëª¨ë¦¬ 리ì¤í¸ë¥¼ ì¶ë ¥í ê²ì´ë¤. ëª ìë ì¤í¬ë¦½í¸ê° ì¤íëê³ ììëë efree()를 ì©í í´ì 를 í´ì ìëë¤. +</simpara> </sect2> <sect2 id="phpdevel-addfunc-symtab"> - <title>Setting Variables in the Symbol Table</title> + <title>ì¬ë³¼ í ì´ë¸ìì ë³ìí ì¤ì </title> <para> - A number of macros are available which make it easier to set a - variable in the symbol table: - + 매í¬ë¡ë¤ì ì«ìë ì¬ë³¼ í ì´ë¸ìì ë ì½ê² ë³ìíì¼ë¡ ì¤ì í ì ìë¤: <itemizedlist> <listitem> <simpara>SET_VAR_STRING(name,value) <footnoteref linkend="symtab-1"/> @@ -207,52 +194,51 @@ <para> <footnote id="symtab-1"> <simpara> - Be careful here. The value part must be malloc'ed manually because - the memory management code will try to free this pointer later. Do - not pass statically allocated memory into a SET_VAR_STRING.</simpara> +ì´ë¶ë¶ì 주ìê¹ê² ë³´ë¼ +ì´ ê°ì ìëì¼ë¡ mallocíì´ì¼ íë¤. ìëíë©´ ë©ëª¨ë¦¬ ê´ë¦¬ ì½ëë ëì¤ì ì´ ë¶ë¶ì +í´ì í ê²ì´ë¤. SET_VAR_STRINGë¡ë¶í° ì§ì ë ë©ëª¨ë¦¬ë¥¼ ì ì ì¼ë¡ ëì§ ë§ìì¼ íë¤.</simpara> </footnote> </para> <simpara> - Symbol tables in PHP 3.0 are implemented as hash tables. At any - given time, &symbol_table is a pointer to the 'main' symbol - table, and active_symbol_table points to the currently active - symbol table (these may be identical like in startup, or - different, if you're inside a function).</simpara> - <para> - The following examples use 'active_symbol_table'. You should - replace it with &symbol_table if you specifically want to work - with the 'main' symbol table. Also, the same functions may be - applied to arrays, as explained below.</para> +PHP 3.0ì ì¬ë³¼ í ì´ë¸ì hash í ì´ë¸ì²ë¼ ì ê³µëë¤. +주ì´ì§ ì´ë¤ ìê°ì &symbol_table ì 'main' ì¬ë³¼ í ì´ë¸ì ê°ë¥´í¤ê³ , +active_symbol_tableì íì¬ ì¤íì¤ì¸ ì¬ë³¼ í ì´ë¸ì ê°ë¥´í¨ë¤. +(ì´ê²ìì ìë§ í¨ìë´ìì ì²ìëë ë¤ë¥¸ëìë ëì¼í ê²ì´ë¤.) +</simpara> <para> + +ë¤ìì 'active_symbol_table'ì ì´ì©í ìì ë¤ì´ë¤. ë¹ì ì´ ëª ííê² 'main' ì¬ë³¼ í ì´ë¸ë¡ ìì í길 ìíë©´ &symbol_tableì¼ë¡ ê·¸ê²ì ëì²´í´ì¼ íë¤. +ë§ì°¬ê°ì§ë¡ ê°ì í¨ìë¤ë ë°°ì´ë ìëì ë°í ê²ì²ë¼ ì ì©ë ê²ì´ë¤. +</para> + <para> <example> - <title>Checking whether $foo exists in a symbol table</title> + <title>ì¬ë³¼í ì´ë¸ë´ $fooê° ì¡´ì¬íëì§ ì²´í¬</title> <programlisting> if (hash_exists(active_symbol_table,"foo",sizeof("foo"))) { exists... } else { doesn't exist } </programlisting> </example> <example> - <title>Finding a variable's size in a symbol table</title> + <title>ì¬ë³¼í ì´ë¸ë´ ë³ìíì í¬ê¸° 찾기</title> <programlisting> hash_find(active_symbol_table,"foo",sizeof("foo"),&pvalue); check(pvalue.type); </programlisting> </example> - - Arrays in PHP 3.0 are implemented using the same hashtables as - symbol tables. This means the two above functions can also be - used to check variables inside arrays.</para> +PHP 3.0ì ë°°ì´ì ì¬ë³¼ í ì´ë¸ì²ë¼ ê°ì í´ìí ì´ë¸ë¡ ì¬ì©íë ê²ì ì ê³µëë¤. +ëê° ì´ìì í¨ìê° ë°°ì´ë´ìì ë³ìíì ì²´í¬íë ê²ì í ì ìë¤ë ë»ì´ë¤. +</para> <simpara> - If you want to define a new array in a symbol table, you should do - the following.</simpara> +ë§ì½ ë¹ì ì¬ë³¼í ì´ë¸ë¤ìì ìë¡ì´ ë°°ì´ì ì ìí길 ìíë©´, ë¤ìê³¼ ê°ì´ í´ì¼ íë¤. +</simpara> <simpara> - First, you may want to check whether it exists and abort - appropiately, using hash_exists() or hash_find().</simpara> + 먼ì ë¹ì ì ì²´í¬í길 ìíë ê²ì´ ì¡´ì¬íë ì§ ì¹ì¸ì´ ì·¨ìëìëì§ hash_exists()ë hash_find()ë¡ íì¸í´ì¼ íë¤. +</simpara> <simpara> - Next, initialize the array:</simpara> +ë¤ì, ë°°ì´ì ì´ê¸°ííë¤:</simpara> <para> <example> - <title>Initializing a new array</title> + <title>ì ë°°ì´ ì´ê¸°í</title> <programlisting> pval arr; @@ -260,14 +246,14 @@ hash_update(active_symbol_table,"foo",sizeof("foo"),&arr,sizeof(pval),NULL); </programlisting> </example> - - This code declares a new array, named $foo, in the active symbol - table. This array is empty.</para> +ì´ ì½ëë íì±íë ì¬ë³¼ í ì´ë¸ë´ìì $fooë ì´ë¦ì¼ë¡ ì ë°°ì´ë¡ ì ì¸ëìë¤. +ì´ ë°°ì´ì ë¹ì´ ìë¤.</para> <simpara> - Here's how to add new entries to it:</simpara> +ì¬ê¸°ë ì ìí¸ë¦¬ì ì¶ê°íë ë²ì´ë¤: +</simpara> <para> <example> - <title>Adding entries to a new array</title> + <title>ì ë°°ì´ì ìí¸ë¦¬ ì¶ê°</title> <programlisting> pval entry; @@ -286,34 +272,31 @@ hash_next_index_insert(arr.value.ht,&entry,sizeof(pval),NULL); </programlisting> </example> - - If you'd like to modify a value that you inserted to a hash, you - must first retrieve it from the hash. To prevent that overhead, - you can supply a pval ** to the hash add function, and it'll be - updated with the pval * address of the inserted element inside the - hash. If that value is NULL (like in all of the above examples) - - that parameter is ignored.</para> +ë§ì½ ë¹ì ì´ ë¹ì ì´ hashì ì½ì í ê°ì ë°ê¾¸ê³ ì¶ë¤ë©´ ë¹ì ì 먼ì hashìì ê·¸ê²ì ë°íí´ìì¼ íë¤. + +To prevent that overhead, +ë¹ì ì pval ** ìì hash ì¶ê° í¨ìì ê³µê¸í ì ìê³ , 그건 hashììì ì¶ê°ë ìììpval * 주ìë¡ ìì ë ì ìë¤. +ë§ì½ ê·¸ ê°ì´ NULL (모ë ìì ê° ìë ê²ì²ë¼)ì´ë©´, ê·¸ ì¸ìë 무ìëë¤. +</para> <simpara> - hash_next_index_insert() uses more or less the same logic as - "$foo[] = bar;" in PHP 2.0.</simpara> +PHP 2.0ìì hash_next_index_insert() "$foo[] = bar;"ê°ì ëì¼í ë¡ì§ì¼ë¡ ì¬ì©ëìë¤.</simpara> <simpara> - If you are building an array to return from a function, you can - initialize the array just like above by doing:</simpara> +ë§ì½ í¨ìë¡ë¶í° ë°íì ìí ë°°ì´ì ë§ë ë¤ë©´, ë¤ìê³¼ ê°ì´ ë°°ì´ì ì´ê¸°íí ì ìë¤: +</simpara> <programlisting> if (array_init(return_value) == FAILURE) { failed...; } </programlisting> <simpara> - ...and then adding values with the helper functions:</simpara> +..ê·¸ë¦¬ê³ helperí¨ìì í¨ê» ê°ì ì¶ê°íë¤ +</simpara> <programlisting> add_next_index_long(return_value,long_value); add_next_index_double(return_value,double_value); add_next_index_string(return_value,estrdup(string_value)); </programlisting> <para> - Of course, if the adding isn't done right after the array - initialization, you'd probably have to look for the array first: - - <programlisting> +ë¬¼ë¡ , ë°°ì´ì´ê¸°íí ì¶ê°íì§ ìê² ë¤ë©´, ë°°ì´ì 먼ì ì°¾ìì¼ íë¤: +<programlisting> pval *arr; if (hash_find(active_symbol_table,"foo",sizeof("foo"),(void **)&arr)==FAILURE) { can't find... } @@ -321,18 +304,19 @@ </programlisting> </para> <simpara> - Note that hash_find receives a pointer to a pval pointer, and not - a pval pointer.</simpara> +hash_findë í¬ì¸í°ìì pvalí¬ì¸í°ì pvalí¬ì¸í° ìëì´ë ë°ëë¤. +</simpara> <simpara> - Just about any hash function returns SUCCESS or FAILURE (except - for hash_exists(), which returns a boolean truth value).</simpara> +ê±°ì 모ë hash í¨ìë SUCCESSë FAILUREë§ ë°ííë¤. (ë¶ë¦° íì¤ê°ì ë°ííë hast_exists()ë ì ì¸íë¤). +</simpara> </sect2> <sect2 id="phpdevel-addfunc-retsimple"> - <title>Returning simple values</title> + <title>ê°ë¨í ê° ë°í</title> <simpara> - A number of macros are available to make returning values from a - function easier.</simpara> +매í¬ë¡ì ì«ìì í¨ìë¡ë¶í° ê°ë¨íê² ë¦¬í´ë°ëê² ê°ë¥íë¤. +</simpara> <para> +RETURN_* 매í¬ë¡ë¤ 모ë ë°íê°ê³¼ í¨ììì ë°íëë ëë ê²ì ì íë¤. The RETURN_* macros all set the return value and return from the function: <itemizedlist> @@ -360,7 +344,7 @@ </itemizedlist> </para> <para> - The RETVAL_* macros set the return value, but do not return. +RETVAL_* 매í¬ë¡ë 리í´ê°ì ì¤ì í ì ìì¼ë, ë°íì ëì§ ìëë¤. <itemizedlist> <listitem> <simpara>RETVAL_FALSE</simpara> @@ -383,36 +367,36 @@ </itemizedlist> </para> <simpara> - The string macros above will all estrdup() the passed 's' - argument, so you can safely free the argument after calling the - macro, or alternatively use statically allocated memory.</simpara> +문ìì´ ì¤í¸ë§ì 's'ì¸ìê° íµê³¼ë 모ë estrdup() ì´ìì¼ ê²ì´ë¤. +ê·¸ë¦¬ê³ , ë¹ì ìì íê² ë¶ë¥¸ 매í¬ë¡ë¥¼ ë¶ë¥¸í ì¸ì를 í´ì 를 í ì ìê±°ë, ë¶ê°ì ì¼ë¡ë +ì§ì ë ë©ëª¨ë¦¬ë¥¼ ì ì ì¼ë¡ ì¬ì©í ì ìë¤. +</simpara> <simpara> - If your function returns boolean success/error responses, always - use RETURN_TRUE and RETURN_FALSE respectively.</simpara> +ë§ì½ ë°íë ë¹ì ì í¨ìê° ì°¸/ê±°ì§ ë¶ë¦° ê°ì ë°ííë©´, ê°ê° RETURN_TRUEì RETURN_FALSE ì¸ì ë ì¬ì©íë¤. +</simpara> </sect2> <sect2 id="phpdevel-addfunc-retcomplex"> - <title>Returning complex values</title> + <title>ìì í ê° ë°í</title> <simpara> - Your function can also return a complex data type such as an - object or an array.</simpara> +ë¹ì ì í¨ìë ì´ë¯¸ ê°ì²´ë ë°°ì´ì ìì í ë°ì´í íì ì 리í´í ì ìë¤. +</simpara> <para> - Returning an object: +ê°ì²´ ë°í: <orderedlist numeration="arabic"> <listitem> - <simpara>Call object_init(return_value).</simpara> + <simpara>object_init(return_value)를 ë¶ë¥¸ë¤.</simpara> </listitem> <listitem> - <para>Fill it up with values. The functions available - for this purpose are listed below.</para> + <para>ê°ì¼ë¡ ì±ì´ë¤. 모ë í¨ìë ìëë¡ ì¶ë ¥ëë ê²°ê³¼ê° ê°ë¥íë¤.</para> </listitem> <listitem> - <para> Possibly, register functions for this object. - In order to obtain values from the object, the function would - have to fetch "this" from the active_symbol_table. Its type - should be IS_OBJECT, and it's basically a regular hash table - (i.e., you can use regular hash functions on .value.ht). The - actual registration of the function can be done using: + <para> +ê°ë¥íë¤ë©´ ì´ ê°ì²´ë¥¼ ìí í¨ìë ë±ë¡ìí¨ë¤. +ê°ì²´ë¡ë¶í° ê°ì ì°¨ë¡ëë¡ í¬í¨íê³ , í¨ìë activ_symbol_tableë¡ë¶í° "this"를 ê°ì§ê³ ìì¼ í ê²ì´ë¤. +ì´ë¤ íì ì IS_OBJECTì´ ìëë©´ ìëê³ , 기본ì ì¼ë¡ ì ê· í´ì í ì´ë¸ì´ì´ì¼ íë¤ +(ì, ë¹ì ì .value.htì²ë¼ ì ê· í´ì í¨ì를 ì¬ì©í ì ìë¤) +í¨ìì ì¤ì ë±ë¡ì ë¤ìê³¼ ê°ì´ í ì ìë¤: <programlisting> add_method( return_value, function_name, function_ptr ); </programlisting> @@ -425,42 +409,43 @@ <itemizedlist> <listitem> <simpara>add_property_long( return_value, - property_name, l ) - Add a property named 'property_name', of - type long, equal to 'l'</simpara> + property_name, l ) - longíì , Iì ëì¼í 'property_name'ì´ë¼ë íë¡í¼í° ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_property_double( return_value, - property_name, d ) - Same, only adds a double</simpara> + property_name, d ) - ëªê°ì doubleíì ë§ ì¶ê°</simpara> </listitem> <listitem> <simpara>add_property_string( return_value, - property_name, str ) - Same, only adds a string</simpara> + property_name, str ) - ëªê°ì stringíì ë§ ì¶ê°</simpara> </listitem> <listitem> <simpara>add_property_stringl( return_value, - property_name, str, l ) - Same, only adds a string of length 'l'</simpara> + property_name, str, l ) - ëªê°ì 'l'길ì´ì ì¤í¸ë§ë§ ì¶ê°'</simpara> </listitem> </itemizedlist> </para> <para> - Returning an array: +ë°°ì´ ë°í: <orderedlist numeration="arabic"> <listitem> - <simpara>Call array_init(return_value).</simpara> + <simpara>array_init ë¶ë¥´ê¸°(return_value).</simpara> </listitem> <listitem> - <simpara>Fill it up with values. The functions available - for this purpose are listed below.</simpara> + <simpara>ê°ì¼ë¡ ì±ì°ê¸°. í¨ìë ìë 목ë¡ì ì¬ì©ì ê°ë¥íê² íë¤.</simpara> </listitem> </orderedlist> </para> <para> + The functions used to populate an array are: <itemizedlist> <listitem> - <simpara>add_assoc_long(return_value,key,l) - add - associative entry with key 'key' and long value 'l'</simpara> + <simpara>add_assoc_long(return_value,key,l) - +'ken'í¤ì 'I'ì longì¼ë¡ ë ê³µë ìí¸ë¦¬ +</simpara> </listitem> <listitem> <simpara>add_assoc_double(return_value,key,d)</simpara> @@ -470,11 +455,13 @@ </listitem> <listitem> <simpara>add_assoc_stringl(return_value,key,str,length,duplicate) - specify the string length</simpara> +ì¤í¸ë§ ê¸¸ì´ ì§ì +</simpara> </listitem> <listitem> - <simpara>add_index_long(return_value,index,l) - add - entry in index 'index' with long value 'l'</simpara> + <simpara>add_index_long(return_value,index,l) - +ìí¸ë¦¬ì 'index' ì¸ë±ì¤ì 'i'ì¼ë¡ ë longì ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_index_double(return_value,index,d)</simpara> @@ -484,11 +471,12 @@ </listitem> <listitem> <simpara>add_index_stringl(return_value,index,str,length) - - specify the string length</simpara> + - 문ìì´ ê¸¸ì´ ì§ì </simpara> </listitem> <listitem> - <simpara>add_next_index_long(return_value,l) - add an - array entry in the next free offset with long value 'l'</simpara> + <simpara>add_next_index_long(return_value,l) - +ë°°ì´ ìí¸ë¦¬ì 'ã £'ì¼ë¡ ë longì ë¤ì free offsetì ì¶ê° +</simpara> </listitem> <listitem> <simpara>add_next_index_double(return_value,d)</simpara> @@ -498,18 +486,17 @@ </listitem> <listitem> <simpara>add_next_index_stringl(return_value,str,length) - - specify the string length</simpara> + - 문ìì´ ê¸¸ì´ ì§ì </simpara> </listitem> </itemizedlist> </para> </sect2> <sect2 id="phpdevel-addfunc-reslist"> - <title>Using the resource list</title> + <title>ìì ëª©ë¡ ì¬ì©í기</title> <simpara> - PHP 3.0 has a standard way of dealing with various types of - resources. This replaces all of the local linked lists in PHP 2.0.</simpara> + PHP 3.0ì ì¬ë¬ ììì ê°ì§ íí를 ë¤ë£¨ë íì¤ì ì¸ ë°©ë²ì ê°ì§ê³ ìë¤. ì´ê²ì PHP 2.0ì 모ë ì§ìì ì¸ linked list를 ëì²´íë¤</simpara> <para> - Available functions: +ê°ë¥í í¨ì: <itemizedlist> <listitem> @@ -581,11 +568,7 @@ <sect2 id="phpdevel-addfunc-prestable"> <title>Using the persistent resource table</title> <para> - PHP 3.0 has a standard way of storing persistent resources (i.e., - resources that are kept in between hits). The first module to use - this feature was the MySQL module, and mSQL followed it, so one - can get the general impression of how a persistent resource should - be used by reading mysql.c. The functions you should look at are: + PHP 3.0ì ì구ì ì¸ ìì(persistent resources; ì, ê·¸ëìì íí¸ì를 ë³´ê´íë ìì)ì ì ì¥íë íì¤ì ì¸ ë°©ë²ì ê°ì§ê³ ìë¤. ì´ ë°©ë²ì MySQL 모ëìì ì²ìì¬ì©ëìê³ , mSQLë ì´ê²ì ë°ë¥´ê³ ìë¤. ë°ë¼ì persistent resource를 ì´ë»ê² ì¬ì©íëê°ì ëí´ ìê³ ì¶ë¤ë©´ ì°ì mysql.c를 ì½ì´ë³´ëë¡íì. 주ìí´ì ë³¼ í¨ìë¤ì ë¤ìê³¼ ê°ë¤: <simplelist> <member>php3_mysql_do_connect</member> @@ -594,7 +577,7 @@ </simplelist> </para> <para> - The general idea of persistence modules is this: +persistence 모ëì ì¼ë°ì ì¸ ideaë ë¤ìê³¼ ê°ë¤: <orderedlist numeration="arabic"> <listitem> <simpara>Code all of your module to work with the @@ -677,17 +660,9 @@ mustn't use efree() here either.</simpara> </sect2> <sect2 id="phpdevel-addfunc-addcfg"> - <title>Adding runtime configuration directives</title> + <title>ë°íì ì¤ì ì§ìì(directives) ì¶ê°</title> <para> - Many of the features of PHP 3 can be configured at runtime. These - configuration directives can appear in either the designated - php3.ini file, or in the case of the Apache module version in the - Apache .conf files. The advantage of having them in the Apache - .conf files is that they can be configured on a per-directory - basis. This means that one directory may have a certain - safemodeexecdir for example, while another directory may have - another. This configuration granularity is especially handy when - a server supports multiple virtual hosts.</para> + ë§ì PHPì 기ë¥(feature)ë¤ì´ ì¤íì¤ì ì¤ì ê°ë¥íë¤. ì´ ì¤ì ì§ìì(configuration directives)ë php3.iniì ì¤ì ëê±°ë, Apache 모ëì ê²½ì° .conf íì¼ì ì¤ì ê°ë¥íëë¡ ëì´ ìë¤. Apache .conf íì¼ì ì¤ì íë ê²ì ì¥ì ì ëë í 리ë³ë¡ ì¤ì ì ë¤ë¥´ê² í ì ìë¤ë ì ì´ë¤. ì´ê²ì ì를ë¤ì´ ì´ë¤ ëë í ë¦¬ê° ë¤ë¥¸ ëë í 리를 ê°ì§ê³ ìì´ë, í´ë¹íë í ëë í 리ìë§ safemodeexecdir ì¤ì ì í ì ìë¤ë ê²ì´ë¤. ì´ ê°ë³ ì¤ì 기ë¥ì ìë²ê° multiple virtual hosts를 ì§ìí ë ë¬´ì² ì ì©íë¤</para> <para> The steps required to add a new directive: @@ -727,10 +702,9 @@ </sect2> </sect1> <sect1 id="calling-user-functions"> - <title>Calling User Functions</title> + <title>ì¬ì©ì í¨ì를 ë¶ë¥´ê¸°</title> <simpara> - To call user functions from an internal function, you should use - the <function>call_user_function</function> function. +ë´ë¶ í¨ì(internal function)ìì ì¬ì©ì í¨ì를 ë¶ë¥´ë ¤ë©´, <function>call_user_function</function>í¨ì를 ì¬ì©íì¬ì¼ íë¤. </simpara> <simpara> <function>call_user_function</function> returns SUCCESS on success, @@ -806,98 +780,73 @@ <sect1 id="phpdevel-errors"> <title>Reporting Errors</title> <simpara> - To report errors from an internal function, you should call the - <function>php3_error</function> function. This takes at least two - parameters -- the first is the level of the error, the second is - the format string for the error message (as in a standard - <function>printf</function> call), and any following arguments - are the parameters for the format string. The error levels are: - </simpara> +ë´ë¶ í¨ììì ìë¬ë¥¼ reportí ëë <function>php3_error</function>í¨ì를 ì¬ì©íë ê²ì´ ì¢ë¤. ì´ í¨ìë ìµì ëê°ì ì¸ì를 ê°ì§ê³ í¸ì¶ëë¤. 첫ë²ì§¸ë ìë¬ì levelì´ê³ , ë¤ë¥¸ íëë ìë¬ ë©ì¸ì§ë¥¼ ìí format string( <function>printf</function>ìì ì¬ì©ëë ê²ê³¼ ê°ì íí) ì´ë¤. ê·¸ë¦¬ê³ ê·¸ ë머ì§ë 주ì´ì§ format stringì parameterê° ëë¤. ìë¬ levelì ë¤ìê³¼ ê°ë¤: </simpara> <sect2 id="internal.e-notice"> <title>E_NOTICE</title> <simpara> - Notices are not printed by default, and indicate that the script - encountered something that could indicate an error, but could also - happen in the normal course of running a script. For example, - trying to access the value of a variable which has not been set, - or calling <function>stat</function> on a file that doesn't exist. +Noticeë 기본ì ì¼ë¡ë ì¶ë ¥ëì§ ìëë¤. ì´ê²ì ì¤í¬ë¦½í¸ê° ëê° ìë¬ë¥¼ ê°ì§íì§ë§, ê·¸ê²ì´ ì ìì ì¸ ìí©ìì ë°ìíë ê²ì´ë¼ë ì미ì´ë¤. ì를ë¤ì´ ì¤ì ëì§ ìì ë³ì를 ì¬ì©íë ¤ íê±°ë, ì¡´ì¬íì§ ìë íì¼ì <function>stat</function>í¨ì를 í¸ì¶íë ê² ë±ì´ë¤. </simpara> </sect2> <sect2 id="internal.e-warning"> <title>E_WARNING</title> <simpara> - Warnings are printed by default, but do not interrupt script - execution. These indicate a problem that should have been trapped - by the script before the call was made. For example, calling - <function>ereg</function> with an invalid regular expression. +Warningì 기본ì ì¼ë¡ ì¶ë ¥ëë¤. ê·¸ë¬ë, ì¤í¬ë¦½í¸ì ì¤íì ë©ì¶ì§ë ìëë¤. ì´ê²ì í¸ì¶ì´ ìë£ë기 ì ì ì¤í¬ë¦½í¸ì ìí´ ì¡íì ¸ì¼ íë 문ì 를 ê°ë¦¬í¨ë¤. ì를ë¤ì´ ì못ë regular expressionì¼ë¡ <function>ereg</function>를 í¸ì¶íë ê² ë±ì´ë¤. </simpara> </sect2> <sect2 id="internal.e-error"> <title>E_ERROR</title> <simpara> - Errors are also printed by default, and execution of the script is - halted after the function returns. These indicate errors that can - not be recovered from, such as a memory allocation problem. - </simpara> +Errorë 기본ì ì¼ë¡ ì¶ë ¥ëë¤. ê·¸ë¦¬ê³ , í¨ìì ì¤íì´ ìë£ë ì§í, ì¤í¬ë¦½í¸ì ì¤íì ë©ì¶ë¤. ì´ê²ì memory allocation 문ì ê°ì ë³µêµ¬ê° ë¶ê°ë¥í ìë¬ë¥¼ ì미íë¤ </simpara> </sect2> <sect2 id="internal.e-parse"> <title>E_PARSE</title> <simpara> - Parse errors should only be generated by the parser. The code is - listed here only for the sake of completeness. +Parse errorë ì¤ì§ Parserë§ì´ ìì±ê°ë¥íë¤. codeê° listëë¤. </simpara> </sect2> <sect2 id="internal.e-core-error"> <title>E_CORE_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated by the core - of PHP. Functions should not generate this type of error. - </simpara> +PHPì coreììí´ ìì±ëë¤ë ì ì ì ì¸íê³ ë E_ERRORì ëì¼íë¤. ì¼ë° í¨ìë¡ë ì´ ííì ìë¬ë¥¼ ë§ë¤ì§ 못íë¤. </simpara> </sect2> <sect2 id="internal.e-core-warning"> <title>E_CORE_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by the core - of PHP. Functions should not generate this type of error. - </simpara> +PHPì coreììí´ ìì±ëë¤ë ì ì ì ì¸íê³ ë E_WARNINGì ëì¼íë¤. ì¼ë° í¨ìë¡ë ì´ ííì ìë¬ë¥¼ ë§ë¤ì§ 못íë¤.</simpara> </sect2> <sect2 id="internal.e-compile-error"> <title>E_COMPILE_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated by the Zend Scripting - Engine. Functions should not generate this type of error. +ì´ê²ì E-Errorë ë¹ì·íë¤, ìì¸ì ì¼ë¡ Zendì¤í¬ë¦½í ìì§ì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-compile-warning"> <title>E_COMPILE_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by the Zend Scripting - Engine. Functions should not generate this type of error. - </simpara> +ì´ê²ì E_WARNINGì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ Zend ì¤í¬ë¦½í ìì§ì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. +</simpara> </sect2> <sect2 id="internal.e-user-error"> <title>E_USER_ERROR</title> <simpara> - This is like an E_ERROR, except it is generated in PHP code by using - the PHP function <function>trigger_error</function>. Functions should - not generate this type of error. +ì´ê²ì E_ERRORì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-user-warning"> <title>E_USER_WARNING</title> <simpara> - This is like an E_WARNING, except it is generated by using the PHP - function <function>trigger_error</function>. Functions should not - generate this type of error. +ì´ê²ì E_WARNINGì´ë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤. </simpara> </sect2> <sect2 id="internal.e-user-notice"> <title>E_USER_NOTICE</title> <simpara> - This is like an E_NOTICE, except it is generated by using the PHP - function <function>trigger_error</function>. Functions should not - generate this type of error. - </simpara> +ì´ê²ì E_NOTICEë ë¹ì·íë¤. ìì¸ì ì¼ë¡ PHP í¨ì<function>trigger_error</function>를 ì´ìíë PHPì½ëì ìí´ ë°ìíë¤. +í¨ìë ì´ ìë¬ì íì ì ë°ìíì§ ìëë¤.</simpara> </sect2> </sect1> </appendix> Index: phpdoc/kr/appendices/regexp.xml diff -u phpdoc/kr/appendices/regexp.xml:1.2 phpdoc/kr/appendices/regexp.xml:1.3 --- phpdoc/kr/appendices/regexp.xml:1.2 Tue Jan 9 16:33:39 2001 +++ phpdoc/kr/appendices/regexp.xml Thu Jan 18 21:26:38 2001 @@ -1,3 +1,3 @@ -<chapt>Regular expressions +<chapt>Regular expressions <sect>Short overview to regexps with pointers to more info Index: phpdoc/kr/chapters/intro.xml diff -u phpdoc/kr/chapters/intro.xml:1.2 phpdoc/kr/chapters/intro.xml:1.3 --- phpdoc/kr/chapters/intro.xml:1.2 Sun Jan 7 10:48:41 2001 +++ phpdoc/kr/chapters/intro.xml Thu Jan 18 21:26:39 2001 @@ -1,18 +1,18 @@ - <chapter id="introduction"> - <title>ìê° (Introduction)</title> + <chapter id="introduction"> + <title>?ëì»» (Introduction)</title> <sect1 id="intro-whatis"> - <title>PHPë 무ìì¸ê°?</title> + <title>PHP? è¾ë뾿?멸??</title> <simpara> - PHP(ê³µìì ì¼ë¡ "PHP: Hypertext Preprocessor ")ë server-side - HTML-embedded scripting languageì ëë¤. + PHP(æ¨ëë?ê³¸ìæ¿¡?"PHP: Hypertext Preprocessor ")??server-side + HTML-embedded scripting language?ë ë²?? </simpara> <para> - ê°ë¨í ëµì´ì§ë§, 무ìì ì미í ê¹? ë¤ì ì를 ë³´ì: + åªê¾¨ë???ëì ï§Âï§? è¾ë뾿???ì??ì¢í´? ?ã ¼ì¬ ?ë? è¹ëì: </para> <para> <example> - <title>ìê°ì© ì문</title> + <title>?ëì»»???ëЦ</title> <programlisting role="php"> <html> <head> @@ -30,13 +30,13 @@ </example> </para> <para> - Perlì´ë Cì ê°ì ë¤ë¥¸ CGI ì¤í¬ë¦½í¸ì ë¬ë¦¬ HTMLì ì¶ë ¥íëë° ë§ì ëª ë ¹ì´ê° íììë¤. - ë¹ì ì HTMLë´ì ë¹ì ì´ íê³ ì íë ì¼(ìì ìì° íì¤ì 문ìì´ ì¶ë ¥)ì ëí ì¤í¬ë¦½í¸ë¥¼ ì ì´ì£¼ë©´ ëë¤. - PHPì½ëë í¹ì í <link linkend="language.basic-syntax.phpmode">ììê³¼ ë íê·¸</link> - ì¬ì´ì ë¤ì´ê°ê² ëëë°, ì´ íí¬ë PHP모ëë¡ ë¤ì´ê°ê±°ë ëì¤ë ê²ì´ë¤. + Perl?ëêµ¹ C? åªì? ?㠻⠨ CGI ?ã ½ê²ç±ìë? ?Ñâ HTML??ç°ìì °?ìë??ï§ë¡®? ï§ë ì¡?ë¿? ?꾩ì?ë ¿ë. + ?ë±ë? HTML?ëë¿ ?ë±ë???ìí¬???ìë ???ê¾©ì½ ?ê³¸ì¦ ?ì쨪??è¾ëªì??ç°ìì °)???Â???ã ½ê²ç±ìëç??곸뼱äºì°ã ?ìë. + PHPè붾뱶???ë±ì ??<link linkend="language.basic-syntax.phpmode">?ììæ¨????ìë </link> + ?Ñì ???㠼뼱åªÂå¯??ìë?? ???ìê²??PHPï§â¤ë±¶æ¿¡??㠼뼱åªÂå«ê³êµ¹ ?ìì¤??å¯ê»ì ?? </para> <para> - PHPê° ë¤ë¥¸ Clien-side Javascripì 구ë³ëë ê²ì ì´ ì½ëê° ìë²ìì ì¤íëë¤ë ê²ì´ë¤. + PHPåªÂ ?㠻⠨ Clien-side Javascrip? æ´Ñí?ìë å¯ê»? ??è붾뱶åªÂ ?ìì¾?ë¨¯ê½ ?㠽뻾?ìë??å¯ê»ì ?? If you were to have a script similar to the above on your server, the client would receive the results of running that script, with no way of determining what @@ -47,15 +47,15 @@ </sect1> <sect1 id="intro-whatcando"> - <title>PHPë¡ ë¬´ìì í ì ìëê°?</title> + <title>PHPæ¿¡?è¾ë뾿???????ëëåªÂ?</title> <para> - ê°ì¥ 기본ì ì¸ ë 벨ìì, PHPë ë¤ë¥¸ CGIíë¡ê·¸ë¨ì´ í ì ìë 모ë ê²ì í ì ìë¤. - from data를 ê°ì ¸ì¤ê³ , ëì ì¸ ì¹íì´ì§ë¥¼ ë§ë¤ê±°ë, Cookie를 ë³´ë´ê³ ë°ì ìë ìë¤. + åªÂ??æ¹²ê³ë¯?ê³¸ì¤ ?ë꺼?먯ê½, PHP???㠻⠨ CGI?ê¾¨ì¤æ´¹ëªì©???????ëë ï§â¤ë±º å¯ê»ì£ ?ì¢ë ?ëë. + from dataç?åªÂ?ëªì¤æ¨? ?ìì»???ë±ë¹?ë?ç?ï§ë®ë±¾å«ê³êµ¹, Cookieç?è¹ëê¶¡æ¨?è«ìì£ ?ìë£ ?ëë. </para> <para> - ìë§ PHPì ê°ì¥ ê°ë ¥íê³ ê´ì¬ì´ ê°ë ë¶ë¶ì ë°ì´íë² ì´ì¤ë¤ì íëì ì§ìì´ë¤. - PHP를 ì¬ì©íë©´ ë¹ì ì Database를 ì¬ì©í ì¹íì´ì§ë¥¼ ëëëë¡ ê°ë¨í ë§ë¤ ì ìë¤. - ë¤ìì ì¼ë°ì ì¸ Databaseë¤ì ì§ìíë¤: + ?꾨ì PHP??åªÂ??åªëº£ì °?ìí¬ æ¿Â?Ñì åªÂ??éºÂéºê¾©? ?ê³ì ?Â踰ì¢ì ?㠻뱾????ê¼»? ï§Â?먯ì ?? + PHPç??Ñì?ìã ?ë±ë? Databaseç??Ñì???ë±ë¹?ë?ç??Â?ë¾ë£æ¿¡?åªê¾¨ë??ï§ë®ë±¾ ???ëë. + ?ã ¼ì¬???ì°ì»²?ê³¸ì¤ Database?ã ¼ì£ ï§Â?먰븳?? <blockquote> <simplelist columns="3"> <member>Adabas D</member> @@ -83,9 +83,9 @@ </blockquote> </para> <para> - PHPë IMAP, SNMP, NNTP, POP3, HTTPë±ì íë¡ì½í¨ê³¼ ë ë¤ë¥¸ ê²ë¤ì ì¬ì©íë - ë¤ë¥¸ ìë¹ì¤ë¤ì ëí´ìë ì´ë¯¸ ì§ìíê³ ìë¤. ì¬ì´ì§ë raw network ìì¼ì ì¬ì©íë©´, - ê·¸ì¸ì ë¤ë¥¸ íë¡í ì½ë¤ì ì¬ì©í ìë ìë¤. + PHP??IMAP, SNMP, NNTP, POP3, HTTP?ê¹ì½ ?꾨ì¤èë·ë§æ¨????㠻⠨ å¯ê»ë±¾???Ñì?ìë + ?㠻⠨ ?ìí¬?㠻뱾???Â?ëê½???ë? ï§Â?먰븯æ¨??ëë. ?Ñë¼±ï§Â??raw network ?ë¯í???Ñì?ìã, + æ´¹ëªì ???㠻⠨ ?꾨ì¤?ì¢í³?ã ¼ì£ ?Ñì???ìë£ ?ëë. </para> <!-- <figure> @@ -100,10 +100,10 @@ </sect1> <sect1 id="intro-history"> - <title>PHPì ìì¬</title> + <title>PHP????ê¶</title> <simpara> - PHPë 1994ë ê°ì &link.rasmus;ê° ì²ì ê³ ìíìë¤. - ì´ê¸° ë¹ê³µê°ë²ì ì ê·¸ì ííì´ì§ì ì¬ëê° ëê° ê·¸ì ì¨ë¼ì¸ ì´ë ¥ì를 ë´¤ëì§ ë³´ê´íëë° ì¬ì©ëìë¤. + PHP??1994??åªÂ??&link.rasmus;åªÂ ï§£ìì¬ æ¨ì¢ë¸?ì??? + ç¥ë린 é®ê¾§ë¬åªìì¾?꾩? æ´¹ëªì½ ?ëë¹?ë????Ñë»åªÂ ?ê¾§? æ´¹ëªì½ ?â¤ìª???ëì °?ì? éã »ëï§Â è¹ë¿??ìë???Ñì?ìë¿?? The first version used by others was available sometime in early 1995 and was known as the Personal Home Page Tools. It consisted of a very