Toorion, I suggest *not* your code becomes unreadable because of PHP
limitations but because of you application architecture limitations.
I see from your example that you're building a Ext.JS datagrid. And,
what is done in the example, is writing in PHP what should be written
in JavaScript. ExtJS
On 2010-03-28, Benjamin Eberlei wrote:
> Index: ext/reflection/php_reflection.c
>===
> --- ext/reflection/php_reflection.c (revision 296963)
> +++ ext/reflection/php_reflection.c (working copy)
> @@ -3425,7 +3425,7 @@
> } el
Hello everyone,
I have created a simple patch that extends PHP ReflectionException
Messages in the case of a missing property or method when calling:
$reflClass->getProperty('notKnown');
$reflClass->getMethod('notKnown');
Currently, in both cases only the unknown property and method name
hi florian,
On Sat, Mar 27, 2010 at 03:28:39PM +0100, Florian Anderiasch wrote:
> The core differences I'm seeing here is:
>
> - DPL (Debian Project Leader) != PHP RM (Release Manager)
> It's actually not even remotely comparable.
what would be more comparable would be the debian RM('s). and
Hi,
There is another solution to this problem, which is sort-of-on-the-table,
and it's named parameters:
$myLongNameObject = new MyLongNameObject(
'property1' => '1',
'property2' => '2',
'property3' => '3',
'property4' => '4',
'property5' => '5',
);
With prop
