Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62196
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error)
Message-ID: <502BC62D.8000405@lsces.co.uk>
Date: Wed, 15 Aug 2012 16:54:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CAEKFTWWmER9FKsCW=3SzhZb16Gno-Xrd=zSSgQuPWStw_sSFeQ@mail.gmail.com> <CAKxcST80H8vWOe3-nvDfc74EC6E6WgS2K24nYbNnWJMTQozd3A@mail.gmail.com> <CANVTSm6sjF9SwjROv8Y5jR=K8CFEivzfOS9d7yGdF9qwqs6aqg@mail.gmail.com> <CAEKFTWWizHi4JGUgOvTSXVCE4e7R3ooKnXo0NRgPc8pFCij3MA@mail.gmail.com> <CALtuQzDr-goh1gzz7Cx6vXwDgY0+_sx39nz+OfJG2orp40rFYw@mail.gmail.com> <CAEKFTWVnrA9H0BNofnOj1n3+gtzrkb1ZB-NhkisO208Kr+Yrrg@mail.gmail.com>
In-Reply-To: <CAEKFTWVnrA9H0BNofnOj1n3+gtzrkb1ZB-NhkisO208Kr+Yrrg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal: use SomeClass::staticMethod
From: lester@lsces.co.uk (Lester Caine)

Giedrius Dubinskas wrote:
> My main aim with this suggestion is readability. I'd like to remove
> unnecessary noise in code where it doesn't add any value to the
> reader. Code is easy to type (especially with good autocompletion) but
> it is read more often then typed and I think that is important. Or is
> it just me?

Depends who is doing the reading? Since a static method should be provided with 
all the data it needs to produce a result, does it actually matter what it is 
called and how it is called? Of cause it does when one is trying to find the 
right descendent method of the class?

I've already been told that the code I'm working on upgrading is archaic but it 
works fine. The bulk of the recent work has been pulling $this out of functions 
and creating a static section for many that handles the results of building a 
hash from the object, or supplying a ready built one. I'm told that it's bad 
practice to include the static functions within the class? But they are an 
integral part of processing the object, or are overridden by functions in the 
descendant objects. So 'staticMethod' has to be the right one for the object 
created, and SomeClass:: depends on the object being created. So how does the 
proposal cope with that type of structure?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk