Style 1.1: Use proper indenting<\/p>\n
while ($x < $z) \r\n{\r\n\tif ($a == 1) \r\n\t{\r\n\t\techo 'A was equal to 1';\r\n\t} \r\n\telse \r\n\t{\r\n\t\tif ($b == 2) \r\n\t\t{\r\n\t\t\t\/\/do something\r\n\t\t} \r\n\t\telse \r\n\t\t{\r\n\t\t\t\/\/do something else\r\n\t\t}\r\n\t}\r\n}\r\n<\/pre>\n <\/p>\n
1.2\r\nwhile ($x < $z) {\r\n\tif ($a == 1) {\r\n\t\techo 'A was equal to 1';\r\n\t} else {\r\n\t\tif ($b == 2) {\r\n\t\t\t\/\/do something\r\n\t\t} else {\r\n\t\t\t\/\/do something else\r\n\t\t}\r\n\t}\r\n}\r\n<\/pre>\nStyle 2.1: Properly indent conditional statements. Always use braces, it will make later additions of more statements easier.<\/p>\n
while ($x < $z) \r\n{\r\n\tif ($a == 1) \r\n\t{\r\n\t\techo 'A was equal to 1';\r\n\t} \r\n\telse \r\n\t{\r\n\t\tif ($b == 2) \r\n\t\t{\r\n\t\t\t\/\/do something\r\n\t\t} \r\n\t\telse \r\n\t\t{\r\n\t\t\t\/\/do something else\r\n\t\t}\r\n\t}\r\n}\r\n<\/pre>\nStyle 2.2<\/p>\n
while ($x < $z) {\r\n\tif ($a == 1) {\r\n\t\techo 'A was equal to 1';\r\n\t} else {\r\n\t\tif ($b == 2) {\r\n\t\t\t\/\/do something\r\n\t\t} else {\r\n\t\t\t\/\/do something else\r\n\t\t}\r\n\t}\r\n}\r\n<\/pre>\n3.1 Function Calls
\nNo space between function names and parenthesis.<\/p>\n
\t$var = myFunction($x, $y);\r\n<\/pre>\n3.2 Function declarations<\/p>\n
Use braces properly, give meaningful names to the parameters, always return values from functions. Avoid printing\/echoing inside functions.<\/p>\n
function myFunction($province, $city = '')\r\n{\r\n\t\/\/indent all code inside here\r\n\treturn $result;\r\n} \r\n<\/pre>\n4. Use comments before a function. Also, use comments before a block [especially if it uses some difficult to understand logic] use PHPDoc style comments that may work like Javadoc to create documentation from your source files<\/p>\n
\/**\r\n *\tshort description of function\r\n *\r\n *\tOptional more detailed description.\r\n *\r\n *\t@param $paramName - type - brief purpose\r\n *\t@param ...\r\n *\t...\r\n *\t@return type and description\r\n *\/\r\n<\/pre>\n5. Use include_once or require_once instead of include or require to include a file that contains common variables, functions, classes.
\n6. PHP tags: always use<\/p>\n
<?php\r\n\r\n ?>\r\n<\/pre>\ninstead of<\/p>\n
<?\r\n\r\n ?>\r\n<\/pre>\n7. to enclose strings use single quote ‘ ‘ rather than double quotes ” “. Try to use . to concate string variables. You can use double quote and put variables inside.<\/p>\n
\t$associative_array['name'];\r\n\t$var='My String';\r\n\t$var2='Very... long... string... ' . $var . ' ...more string... ';\r\n\t$sql=\"INSERT INTO mytable (field) VALUES ('$var')\";\r\n<\/pre>\n8. Follow some conventions for variable and function names<\/p>\n
From: http:\/\/sitestree.com\/?p=3535
Categories:Root
Tags:
Post Data:2016-07-08 16:04:58<\/p>\n
\t\tShop Online: https:\/\/www.ShopForSoul.com\/<\/a> Style 1.1: Use proper indenting while ($x < $z) { if ($a == 1) { echo ‘A was equal to 1’; } else { if ($b == 2) { \/\/do something } else { \/\/do something else } } } 1.2 while ($x < $z) { if ($a == 1) { echo ‘A was … <\/p>\n
\n\t\t(Big Data, Cloud, Security, Machine Learning): Courses: http:\/\/Training.SitesTree.com<\/a>
\n\t\tIn Bengali: http:\/\/Bangla.SaLearningSchool.com<\/a>
\n\t\thttp:\/\/SitesTree.com<\/a>
\n\t\t8112223 Canada Inc.\/JustEtc: http:\/\/JustEtc.net (Software\/Web\/Mobile\/Big-Data\/Machine Learning) <\/a>
\n\t\tShop Online: https:\/\/www.ShopForSoul.com\/<\/a>
\n\t\tMedium: https:\/\/medium.com\/@SayedAhmedCanada <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"