$Object = new A();$Object->MyMethod(); - created an object
A::MyMethod() - didn’t create any object

And what is not clear from the documentation?

I’ve written it. I cannot understand what the advantage is in comparison with usual method shown as #1.

$Object = new A();$Object->MyMethod(); - created an object
A::MyMethod() - didn’t create any object

And what if I haven’t created an object?

What is the benefit from usage?
Should classes be used as name spaces, for instance?

What do you mean? When is it needed? What tasks are solved this way more effectively?

$Object = new A();$Object->MyMethod(); - created an object
A::MyMethod() - didn’t create any object

Method 1: create an object and use other methods of this object with its data.
Method 2: don’t create any object, use class as a set of functions, for instance, define a class for handling strings and use single functions only without creating object STR::cut(), STR::dup() etc...

mmwfan,
namespace gains an ability to use methods and variables depending on the context.

In the documentation concerning static methods is written that such a method is used for ability to call method without creating an object. Why shouldn’t we declare all the methods like this? We could use static ones only.

Not many manuals are needed, just a couple of examples are enough to understand – usage of static methods is really justified here.

mmwfan, class is a description and object is a concrete specimen of a class possessing the behavior described. But how does it help me?

n00bphp, selmahyekishot, it’s clear now, thanks. By the time I haven’t found any applying for that except for methods archive.

Keeper, look up in Google expression ‘programming patterns’. Programming language doesn’t matter. And you’ll see another applying of classes.

Keeper,

From practical point of view variant including object creation enables evading of class description. You are to declare interface only. It means we can replace a class every moment and none will mention it. I also asked myself about it when writing a big project. Finally I force myself to evade static methods. And if I have to use them I apply experience I got when writing windows programs. It means I create Application object which initiates everything requiring all singletons and deciding which one should be called. After that it calls the necessary module and transmits all these data to it along with a link to itself. The module proves not to know what class is there – the main thing is that everything functions properly. Even if you need to change singleton it is done in one place only.

Do you want any example? I have such. There are a lot of frameworks now. But none of them suits properly. And so you have to write something on your own. And when you find something better and ready-made you start changing everything in hurry. So I have instilled privilege system into a project. And later I found a good solution within one framework. I extracted necessary files, wrote an adapter and changed one string (name) within Application. That’s all. The project hasn’t mentioned that it wasn’t a class.

Of course, someone may say that we could replace a class with statics as well. However this class is used not in one project only as far as it is a part of a framework. And I risk being abused by my colleagues working over the next project for changing components of a framework.

There are a lot of manuals about it but your own experience is quite a different thing 

Having some experience you can always evade overt creating an object in code and use its suspended initialization at the same time.

Last edited by monkeydude (February 26, 2007 11:40 am)

If you need some examples, you’d better use this. The difference is visible at once.

<?php
class api {
public function setReturnPath() {
$this->session['returnPath'][$this->mDir] = getenv('REQUEST_URI');
}
}


class module {
public $session;
public $mDir="moduleDir";

public function showReturnPath() {
echo $this->session['returnPath'][$this->mDir];
exit();
}

function __construct() {
global $_SESSION;

$this->session = &$_SESSION;
api::setReturnPath();
$this->showReturnPath();
}
}

?>

It is use for reduce the code..........