<commit_before><appendix id="coding-standard">
  <title>Zend Framework Coding Standardfor PHP</title>
    <sect1 id="coding-standard.overview">
        <title>Overview</title>

        <sect2 id="coding-standard.overview.scope">
            <title>Scope</title>

            <para>
                This document provides guidelines for code formatting and documentation to individuals
                and teams contributing to Zend Framework. Many developers using Zend Framework have also
                found these coding standards useful because their code's style remains consistent with all
                Zend Framework code. It is also worth noting that it requires significant effort to fully
                specify coding standards.
                
                Note: Sometimes developers consider the establishment of a standard more important than what that
                standard actually suggests at the most detailed level of design. The guidelines in the Zend Framework
                coding standards capture practices that have worked well on the ZF project. You may modify these standards
                or use them as is in accordance with the terms of our <a href="http://framework.zend.com/license">license</a>
            </para>
            <para>
                Topics covered in the ZF coding standards include:

                <itemizedlist>
                    <listitem>
                        <para>PHP File Formatting</para>
                    </listitem>

                    <listitem>
                        <para>Naming Conventions</para>
                    </listitem>

                    <listitem>
                        <para>Coding Style</para>
                    </listitem>

                    <listitem>
                        <para>Inline Documentation</para>
                    </listitem>
                </itemizedlist>
            </para>
        </sect2>

        <sect2 id="coding-standard.overview.goals">
            <title>Goals</title>

            <para>
                Coding standards are important in any development project, but they are particularly important
                when many developers are working on the same project. Coding standards
                help ensure that the code is high quality, has fewer bugs, and can be easily maintained.
            </para>
        </sect2>
    </sect1>

    <sect1 id="coding-standard.php-file-formatting">
        <title>PHP File Formatting</title>

        <sect2 id="coding-standard.php-file-formatting.general">
            <title>General</title>

            <para>
                For files that contain only PHP code, the closing tag ("?>") is never permitted.  It is
                not required by PHP, and omitting it prevents the accidental injection of trailing whitespace into the response.
            </para>

            <para>
                <emphasis>IMPORTANT:</emphasis> Inclusion of arbitrary binary data as permitted by <code>__HALT_COMPILER()</code>
                is prohibited from PHP files in the Zend Framework project or files derived from them. Use of
                this feature is only permitted for some installation scripts.
            </para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.indentation">
            <title>Indentation</title>

            <para>Indentation should consist of 4 spaces. Tabs are not allowed.</para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.max-line-length">
            <title>Maximum Line Length</title>

            <para>
                The target line length is 80 characters. That is to say, ZF developers should strive keep each line of their code
                under 80 characters where possible and practical. However, longer lines are
                acceptable in some circumstances. The maximum length of any line of PHP code is 120 characters.
            </para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.line-termination">
            <title>Line Termination</title>

            <para>
                Line termination follows the Unix text file convention. Lines must end
                with a single linefeed (LF) character. Linefeed characters are represented as ordinal 10, or hexadecimal 0x0A.
            </para>

            <para>
            	Note: Do not use carriage returns (CR) as is the convention in Apple OS's (0x0D) or the carriage
            	return/linefeed combination (CRLF) as is standard for the Windows OS (0x0D, 0x0A).
            </para>
        </sect2>
    </sect1>

    <sect1 id="coding-standard.naming-conventions">
        <title>Naming Conventions</title>

        <sect2 id="coding-standard.naming-conventions.classes">
            <title>Classes</title>

            <para>
                Zend Framework standardizes on a class naming convention whereby the names
                of the classes directly map to the directories in which they are stored.
                The root level directory of the ZF standard library is the "Zend/" directory, whereas
                the root level directory of the ZF extras library is the "ZendX/" directory. All 
                Zend Framework classes are stored hierarchially under these root directories..
            </para>

            <para>
                Class names may only contain alphanumeric characters. Numbers are permitted
                in class names but are discouraged in most cases. Underscores are only permitted in place
                of the path separator; the filename "Zend/Db/Table.php" must map to the
                class name "Zend_Db_Table".
            </para>

            <para>
                If a class name is comprised of more than one word, the first letter of each new
                word must be capitalized.  Successive capitalized letters are not allowed, e.g.
                a class "Zend_PDF" is not allowed while "Zend_Pdf" is acceptable.
            </para>
            
            <para>
            	These conventions define a pseudo-namespace mechanism for Zend Framework. Zend Framework
            	will adopt the PHP namespace feature when it becomes available and is feasible for our developers to use in their applications.<commit_msg>Documentation:  - typo fixed<commit_after><appendix id="coding-standard">
  <title>Zend Framework Coding Standardfor PHP</title>
    <sect1 id="coding-standard.overview">
        <title>Overview</title>

        <sect2 id="coding-standard.overview.scope">
            <title>Scope</title>

            <para>
                This document provides guidelines for code formatting and documentation to individuals
                and teams contributing to Zend Framework. Many developers using Zend Framework have also
                found these coding standards useful because their code's style remains consistent with all
                Zend Framework code. It is also worth noting that it requires significant effort to fully
                specify coding standards.
                
                Note: Sometimes developers consider the establishment of a standard more important than what that
                standard actually suggests at the most detailed level of design. The guidelines in the Zend Framework
                coding standards capture practices that have worked well on the ZF project. You may modify these standards
                or use them as is in accordance with the terms of our <a href="http://framework.zend.com/license">license</a>
            </para>
            <para>
                Topics covered in the ZF coding standards include:

                <itemizedlist>
                    <listitem>
                        <para>PHP File Formatting</para>
                    </listitem>

                    <listitem>
                        <para>Naming Conventions</para>
                    </listitem>

                    <listitem>
                        <para>Coding Style</para>
                    </listitem>

                    <listitem>
                        <para>Inline Documentation</para>
                    </listitem>
                </itemizedlist>
            </para>
        </sect2>

        <sect2 id="coding-standard.overview.goals">
            <title>Goals</title>

            <para>
                Coding standards are important in any development project, but they are particularly important
                when many developers are working on the same project. Coding standards
                help ensure that the code is high quality, has fewer bugs, and can be easily maintained.
            </para>
        </sect2>
    </sect1>

    <sect1 id="coding-standard.php-file-formatting">
        <title>PHP File Formatting</title>

        <sect2 id="coding-standard.php-file-formatting.general">
            <title>General</title>

            <para>
                For files that contain only PHP code, the closing tag ("?>") is never permitted.  It is
                not required by PHP, and omitting it prevents the accidental injection of trailing whitespace into the response.
            </para>

            <para>
                <emphasis>IMPORTANT:</emphasis> Inclusion of arbitrary binary data as permitted by <code>__HALT_COMPILER()</code>
                is prohibited from PHP files in the Zend Framework project or files derived from them. Use of
                this feature is only permitted for some installation scripts.
            </para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.indentation">
            <title>Indentation</title>

            <para>Indentation should consist of 4 spaces. Tabs are not allowed.</para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.max-line-length">
            <title>Maximum Line Length</title>

            <para>
                The target line length is 80 characters. That is to say, ZF developers should strive keep each line of their code
                under 80 characters where possible and practical. However, longer lines are
                acceptable in some circumstances. The maximum length of any line of PHP code is 120 characters.
            </para>
        </sect2>

        <sect2 id="coding-standard.php-file-formatting.line-termination">
            <title>Line Termination</title>

            <para>
                Line termination follows the Unix text file convention. Lines must end
                with a single linefeed (LF) character. Linefeed characters are represented as ordinal 10, or hexadecimal 0x0A.
            </para>

            <para>
            	Note: Do not use carriage returns (CR) as is the convention in Apple OS's (0x0D) or the carriage
            	return/linefeed combination (CRLF) as is standard for the Windows OS (0x0D, 0x0A).
            </para>
        </sect2>
    </sect1>

    <sect1 id="coding-standard.naming-conventions">
        <title>Naming Conventions</title>

        <sect2 id="coding-standard.naming-conventions.classes">
            <title>Classes</title>

            <para>
                Zend Framework standardizes on a class naming convention whereby the names
                of the classes directly map to the directories in which they are stored.
                The root level directory of the ZF standard library is the "Zend/" directory, whereas
                the root level directory of the ZF extras library is the "ZendX/" directory. All 
                Zend Framework classes are stored hierarchially under these root directories..
            </para>

            <para>
                Class names may only contain alphanumeric characters. Numbers are permitted
                in class names but are discouraged in most cases. Underscores are only permitted in place
                of the path separator; the filename "Zend/Db/Table.php" must map to the
                class name "Zend_Db_Table".
            </para>

            <para>
                If a class name is comprised of more than one word, the first letter of each new
                word must be capitalized.  Successive capitalized letters are not allowed, e.g.
                a class "Zend_PDF" is not allowed while "Zend_Pdf" is acceptable.
            </para>
            
            <para>
                These conventions define a pseudo-namespace mechanism for Zend Framework. Zend Framework
                will adopt the PHP namespace feature when it becomes available and is feasible for our developers to use in their applications.
            </para>
{'fraction_non_alphanumeric': 0.06397146254458977, 'fraction_numerical': 0.005707491082045184, 'mean_word_length': 1.8223713646532438, 'pattern_counts': {'":': 0, '<': 184, '<?xml version=': 0, '>': 186, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6337548', 'n_tokens_mistral': 3078, 'n_tokens_neox': 2787, 'n_words': 1224}