KevinSchoenmayer/GseTDDUebungKCLR
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial Commit

Browse Source
This commit is contained in:
Riley Schneider
2025-12-03 16:38:10 +01:00
parent c5e26bf594
commit b732d8d4b5
17680 changed files with 5977495 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
database/php/pear/PHP/CodeSniffer/Standards/PEAR/Docs/NamingConventions/ValidClassNameStandard.xml Normal file
View File

@@ -0,0 +1,23 @@
<documentation title="Class Names">
<standard>
<![CDATA[
Classes should be given descriptive names. Avoid using abbreviations where possible. Class names should always begin with an uppercase letter. The PEAR class hierarchy is also reflected in the class name, each level of the hierarchy separated with a single underscore.
]]>
</standard>
<code_comparison>
<code title="Examples of valid class names">
<![CDATA[
Log
Net_Finger
HTML_Upload_Error
]]>
</code>
<code title="Examples of invalid class names">
<![CDATA[
log
NetFinger
HTML-Upload-Error
]]>
</code>
</code_comparison>
</documentation>

23
database/php/pear/PHP/CodeSniffer/Standards/PEAR/Docs/NamingConventions/ValidFunctionNameStandard.xml Normal file
View File

@@ -0,0 +1,23 @@
<documentation title="Function and Method Names">
<standard>
<![CDATA[
Functions and methods should be named using the "studly caps" style (also referred to as "bumpy case" or "camel caps"). Functions should in addition have the package name as a prefix, to avoid name collisions between packages. The initial letter of the name (after the prefix) is lowercase, and each letter that starts a new "word" is capitalized.
]]>
</standard>
<code_comparison>
<code title="Examples of valid function names">
<![CDATA[
connect()
getData()
buildSomeWidget()
XML_RPC_serializeData()
]]>
</code>
<code title="Examples of invalid function names">
<![CDATA[
Connect()
get_data()
]]>
</code>
</code_comparison>
</documentation>