On Wed, Apr 21, 2010 at 10:36:55AM -0700, Stanislav Malyshev wrote:
> Hi!
>
> > \_array\merge($array, $array2);
> > \_string\len($string);
>
> how it's better or more clean than array_merge or strlen? I am a big fan
> of OO and use it all the time, but there's a virtue in moderation - if
Hi!
It is not. It would, however, be a way to fix stuff like argument
ordering inconsistencies without causing a BC break.
Well, let the hundred flowers bloom - if somebody writes an extension
that does that - provided that old ones still in place - we could see if
it proves popular or not. RF
Hi!
\_array\merge($array, $array2);
\_string\len($string);
how it's better or more clean than array_merge or strlen? I am a big fan
of OO and use it all the time, but there's a virtue in moderation - if
you just want a length of a string, you son't have to build class
hierac
Hi!
You know, there is a world out there too, outside the "deep and wide
class hierarchies". I really doubt that namespaces were introduced in
the language with the sole purpose of grouping hundreds of classes. But
you can, if you make everything a class.
Of course, you know much more that I d
Hi,
There is already a convention that reserved (magic) function names start
with __ (double underscore). This may be extended to reserved namespaces, as
I pointed out in the original message. Then, one can use say *__array* as it
is, or can alias it with a shorthand notation. Maybe we can turn to
Sean Coates wrote:
I don't believe there's anything stopping you (or other users) from creating either
userspace or extension wrappers to handle organization and consistency. You could even
use the "system" namespaces, since they don't exist.
True, the thought has crossed my mind. But I'm mor
On Wed, Apr 21, 2010 at 04:18:47PM +0200, Jacob Oettinger wrote:
>
> On 21/04/2010, at 16.03, Stan Vassilev wrote:
> >
> > Ahem. We all secretly know how it should've been from the very start.
> > Pseudo-methods for the basic types.
> >
> > $array->merge($array2);
> > $string->len();
> >
>
>
On 21/04/2010, at 16.03, Stan Vassilev wrote:
>
> Ahem. We all secretly know how it should've been from the very start.
> Pseudo-methods for the basic types.
>
> $array->merge($array2);
> $string->len();
>
Yes. Maybe implemented so that they can be called like functions in a namespace
for ea
> > 4. PARAMETER ORDER.
> Two letters: BC.
> Changing variable order in an existing function is a big fat BC break.
> And
> if we put such a bomb into a new version, what would be the incentive
> for
> people to use it? So that apps would have to be shipped in 2 versions,
> for
> the old php
> No, it is not hard to write strlen but I would also like to see these
> functions organized better. I've felt that PHP has been a mess since I
> learned it way back when, the naming inconsistencies are everywhere.
I don't believe there's anything stopping you (or other users) from creating
ei
Come on. Is it really that hard to write strlen? Or array_merge? Would it
be better if they were len (of what?) and merge (what?)? I don't think so.
Ahem. We all secretly know how it should've been from the very start.
Pseudo-methods for the basic types.
$array->merge($array2);
$string->len
On Wed, 21 Apr 2010, Ryan Panning wrote:
> > > 4. PARAMETER ORDER.
> > Two letters: BC.
> > Changing variable order in an existing function is a big fat BC break. And
> > if we put such a bomb into a new version, what would be the incentive for
> > people to use it? So that apps would have to be s
On 21.04.2010, at 15:24, Ryan Panning wrote:
>>> 2. TYPE HINTING.
>> This topic was discussed to death on the list, please read the archives. If
>> after that you still do not understand what it is about, or have some
>> comments, please ask then.
>
> Sure, it has been discussed over and over
Stanislav Malyshev wrote:
1. SYSTEM NAMESPACES.
Come on. Is it really that hard to write strlen? Or array_merge? Would
it be better if they were len (of what?) and merge (what?)? I don't
think so.
No, it is not hard to write strlen but I would also like to see these
functions organized bett
Sorry for long delay...
On 03/29/2010 09:19 AM, Victor Bolshov wrote:
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 th
On 21 April 2010 11:46, Adi Nita wrote:
> I cannot agree with the idea of preferring
> working applications to good working applications.
Except that's not what's at stake. The application does not become one
bit better or worse by using an updated function that's more
consistent with other funct
Hi,
On Wed, Apr 21, 2010 at 3:20 AM, Stanislav Malyshev wrote:
Come on. Is it really that hard to write strlen? Or array_merge? Would it be
> better if they were len (of what?) and merge (what?)? I don't think so.
I think you missed the point when I said we should use system namespaces.
There
Le 17 avril 2010 18:43, Jérôme Loyet a écrit :
>
> Le 15 avril 2010 12:09, Jérôme Loyet a écrit :
> > hi
> >
> > I made the first release of the patch to convert fpm syntax from xml to ini.
> >
> > Everything is in the RFC: http://wiki.php.net/rfc/fpm/ini_syntax
> > The patch is directly viewable
18 matches
Mail list logo
