Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Simply. I have an empty page looking like
<?php
include("header.php");
include("footer.php");
?>
That gives navbar, config files, pageload took: blabla. And stuff like that. But, what’s the pros, and cons of doing so? Instead of, examplewise, putting it all into one file.
The largest pro I could think of is keeping code clean, and rather then necessarily copying and pasting the code in each individual file you can have it all in one place. Makes it a ton easier to make small changes.
The largest con I can think of is if you’re looking for an error that happens to be in a different file. Since php pages are compiled server side you cannot just click view source to find it.