That doesn’t make sense, at least not without an explanation. If you saw it somewhere and didn’t explain why, ignore it, possibly it is the person’s taste. If you have an explanation, then if you understand the basics you can assess whether it makes sense or not.
If you don’t use the include
load the auxiliary files to that application in what way? Have other similar words, but does essentially the same. There are ways of automatic loading. What may be questionable is its use. And if it exists, it’s because of the structural failure of language. It has nothing to do with object orientation. Actually little of what people think about OOP really is OOP, and a lot of OO people don’t know even though they think they’re using this paradigm.
The include
carries a source code, the use
enables the use of a namespace. A namespace is just a way to organize codes with a surname to facilitate access and disambiguate equal names that do different things. The codes are more physical, the namespaces are more logical. Has a question on the subject in another language, but the basic idea is the same.
Even the use
has to do with modularization not object-oriented.
Every time someone talks about procedural X OOP in PHP there’s a chance that the person doesn’t understand about OOP and uses it just because it’s fashionable, so she thinks that if she does procedural she’s doing something wrong, which is far from true, especially in PHP.
Well I used it in the program: <?php namespace site; include_once 'site/modulo1/Pessoa.php'; use site modulo1 Pessoa; use DAO Connection;
– user65509