1 Identifier naming and definition
1.1 General naming rules
Rule 1.1.1 Do not use Chinese Pinyin
1.2 File naming rules
Rule 1.2.1 Capitalize the first letter of a word (such as UserManage)
1.3 Class naming rules
Rule 1.3.1 Capitalize the first letter of a word (such as UserManage)
1.4 Function naming rules
Rule 1.4.1 Capitalize the first letter of other words except the first word (such as userManage)
1.5 Variable naming rules
Rule 1.5.1 uses underscores between words (such as user_manage)
1.6 Common naming rules
Rule 1.6.1 foreach naming rules, adopt the following method (data can be other names, keys must be k, k1, k2, etc., etc. must be v, v1, v2, etc.):
foreach ($data as $k => $v) {
foreach ($v as $k1 => $v1) {
$t[$k1][$k]=$v1;
}
}
Rule 3.6.2 for naming rule, adopt the following method (the variable must be i, i1):
for ($i=0; $i<8;$i ) {
for ($i1=0; $i1<8;$i1 ) {
}
}
Rule 1.6.3 Function return value naming rules (internal interface, only functions for adding, deleting, and modifying data operations), adopt the following method (the return value variable of the function must be $ret, where $ret['res'] is the return value value, $ ret['msg'] is the error message):
public function addUser(){
…
$data=…
$ret[‘res’]=$data;
$ret[‘msg’]=’Operation failed! ’;
return $ret;
}
Rule 1.6.4 If a variable is used less than 4 times, the variable shall be named $temp (except in the specific cases above)
Rule 1.6.5 How to use single and double quotes, single quotes are preferred (such as $ret['msg'] ='Operation failed!';, $a=eavl("$ ret ['msg'] ='Operation failed!' ;")), exceptions can be made in special circumstances (such as single quotes must be used for strings in sql statements)
Rule 1.6.6 The method name for adding data starts with add, the method name for updating data starts with edit, and the method name for deleting data starts with remove
Rule 1.6.7 For other naming, please check the excel table
1.7 Database naming rules
Rule 1.7.1 The database name uses underscores between words (such as user_manage)
Rule 1.7.1 Table names use underscores between words (such as user_manage)
Rule 1.7.1 Field names use underscores between words (such as user_manage)