cvs: php4 / CODING_STANDARDS

ronabop Wed Oct 18 00:34:56 2000 EDT Modified files: /php4 CODING_STANDARDS Log: As per andi, similar names are for legacy reasons only. Index: php4/CODING_STANDARDS diff -u php4/CODING_STANDARDS:1.3 php4/CODING_STANDARDS:1.4 --- php4/CODING_STANDARDS:1.3 Tue Oct 17 20:00:07 2000 +++ php4/CODING_STANDARDS Wed Oct 18 00:34:56 2000 @@ -162,23 +162,17 @@ And yes, please keep everything on a single line, even if that line is massive. -User Aliases --------------------- -You may also have some user-level aliases with close to duplicate +Aliases & Legacy Documentation +----------------------------------- +You may also have some deprecated aliases with close to duplicate names, for example, somedb_select_result and somedb_selectresult. For documentation puposes, these will only be documented by the most -clearly separated name, with the aliases listed in the documentation for +current name, with the aliases listed in the documentation for the parent function. For ease of reference, user-functions with completely different names, that alias to the same function (such as highlight_file and show_source), will be separately documented. The proto should still be included, describing which function is aliased. - -Legacy Documentation --------------------- -In order to retire older function naming conventions, older -function name variants, when changed, will only be documented under -their current function name, as aliases. Backwards compatible functions -and names should be maintained as long as the code can be reasonably -be kept as part of the codebase. See /phpdoc/README for me information -on documentation. +Backwards compatible functions and names should be maintained as long +as the code can be reasonably be kept as part of the codebase. See +/phpdoc/README for me information on documentation.