Proper include design practice in PHP -
Proper include design practice in PHP -      i've started working on larger preexisting code  base of operations (php) , has come  attending lot of these files  utilize includes/requires in unreadable way. includes/requires sort of cascade through file system, because every file in  scheme includes/requires file called common.php.  mutual file includes/requires every other file, seems when developer in doubt, included/required  mutual , called good.   this written professional web developers, , i'm still student, i'm curious if  mutual practice in php. in php should there  mutual file includes/requires everything, should each file included/required case case, or there different way  mutual practice?   on side note: i'm trying switch out api file new 1 (while keeping old compatibility testing), ,  hard me tell files  utilize new api or old one.        generally, includes should used view based material (html, smarty, perhaps xml or xslt) in mark used  build view in mvc a...