Design - Consolidando meus arquivos PHP?

Question

Meu entendimento é que "nome" .class.php é convenção padrão para criar classes no PHP e, consequentemente, eu tenho um arquivo separado para cada classe.O que eu gostaria de fazer é consolidar minha pequena hierarquia de classe PHP em um único arquivo ... Diga consolidada.class.php.

Isso facilitará o upload / download para o servidor + Se eu precisar executar uma simples pesquisa textual, não tenho que olhar em mais de um arquivo.Além disso, eu posso remover incluir / exigir, já que eu estou essencialmente inserindo-os manualmente.

A questão é, posso consolidar sem dar um sucesso?

editar / update

Muito tempo depois, estou usando arquivos separados e um autoloader.Isso deve ser mais eficiente, mas é claro, quanto depende do tamanho dos arquivos.

Answer 1

The reason people use the one class per file convention is for class autoloaders. This allows your script to automatically only load code that is actually being used by your script in that particular instance. If you load ALL of you classes every time a page loads, it's a fairly inneficient way to go.

For more information about class autoloaders:

http://php.net/manual/en/language.oop5.autoload.php

http://php.net/manual/en/function.spl-autoload-register.php

Answer 2

I believe it depends on the size of the project. You can start small, with everything in just a single file, then, as the code accumulates and you get a better understanding of the domain you're modelling, you can extract units into separate files.

The convention to use a class per file comes from the Java world. For years, PHP has tried to imitate Java, however, some of the practices are absurd. Like, you can't have functions, just classes, even if they're nothing more than a collection of static methods.

Here's an example of a web framework, called Konstrukt, that uses multiple units (classes/functions/constants) per file and seems to be doing well.

As @Nabeel said, you may hit a point where you'd have problems locating code if everything is inside a single big file. Judge by the project you're developing.

Regarding performance, you'd have to benchmark, as once again it depends on the project, but require/include incur some performance overhead due to file I/O. So it might be better that you have a single file loaded per request. The actual parsing might be faster than the system calls that look for the file to require.

Answer 3

I would advise you not to do this because everything a page gets viewed, every single one of your classes is loaded. When using only a few classes which are loaded everytime, it does indeed make no difference performance-wise, but if you have quite a lot of classes and you only use a handful, depending on the page being loaded, you add a huge overload to the page.

Answer 4

I don't want to say the same things like others (which is actually correct ^^) to bring u some new ideas.

I would create few functions to include/require my class files.

Example:

you have 2 php-files:

1: login.php

2: register.php

<?php
   // login.php
   include '../system/functions/myFunctions.php';  
   loadMyClasses(1);
?>

<?php
  // register.php
  include '../system/functions/myFunctions.php';
  loadMyClasses(2); 
?>

<?php
  //myFunctions.php

  DEFINE("CLASS_PATH", "../system/class/");      

  function loadMyClasses($type_id)
  {  
     //Example: Load in everytime. These files are always required.
     require_once CLASS_PATH.'class.database.php';
     require_once CLASS_PATH.'class.sql.php';

     if($type_id == 1)
     {
           require(CLASS_PATH.'class.security.php');
           require(CLASS_PATH.'class.cryptor.php');   
           require(CLASS_PATH.'class.login.php');   
     }

     if($type_id == 2)
     {
           require(CLASS_PATH.'class.security.php'); 
           require(CLASS_PATH.'class.register.php');  
     }
  }
?>

And this way you can simply change the path of the class or interface files. You have to make changes only in one file.

I Hope, I was able to help a bit!