>>> For those that do not understand very well the explanation of jvlad...
>>>
>>> He's suggesting to change the class struct to be an scope struct, and
>>> have a property that tells if it's a namespace or a class, and reuse
>>> the implementation of class which already works very well.
>>> The ne
On 29.09.2008, at 00:21, Gregory Beaver wrote:
Lukas Kahwe Smith wrote:
On 24.09.2008, at 01:17, Guilherme Blanco wrote:
For those that do not understand very well the explanation of
jvlad...
He's suggesting to change the class struct to be an scope struct,
and
have a property that te
Lukas Kahwe Smith wrote:
>
> On 24.09.2008, at 01:17, Guilherme Blanco wrote:
>
>> For those that do not understand very well the explanation of jvlad...
>>
>> He's suggesting to change the class struct to be an scope struct, and
>> have a property that tells if it's a namespace or a class, and r
I share your thoughts and yes namespaces are needed and wanted, but what's
implemented at the moment is quite far from what I'd call a namespace. I
need and want to see there all language entities including variables,
constants, classes, interfaces, and functions. Want to see them all
supported
>
> or just leave the organization of things to classes (with long class
> names with a nice prefix to prevent collissions) and leave it to
> class_alias() (and equivalent features for functions .. also with the
> option of a compile time aliasing) to handle the aliasing.
>
> this removes the ne
On 24.09.2008, at 01:17, Guilherme Blanco wrote:
For those that do not understand very well the explanation of jvlad...
He's suggesting to change the class struct to be an scope struct, and
have a property that tells if it's a namespace or a class, and reuse
the implementation of class which a
""Steph Fox"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> For those that do not understand very well the explanation of jvlad...
>
> Guileherme, you are missing the point. We'd all like to see PHP 5.3.0 out
> there. It has a lot to offer, but namespace support is very obviousl
""Guilherme Blanco"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> For those that do not understand very well the explanation of jvlad...
>
> He's suggesting to change the class struct to be an scope struct, and
> have a property that tells if it's a namespace or a class, and reuse
Federico Lebron wrote:
Tony Bibbs wrote:
I disagree here...it is both wanted and and needed. This feature has
been promised to the community for quite some time now and I'd simply
remind you you do have the option of *not* using namespaces if you
don't want too. If you like REALLY_LONG_CLASS
Tony Bibbs wrote:
I disagree here...it is both wanted and and needed. This feature has been promised to the community for quite some time now and I'd simply remind you you do have the option of *not* using namespaces if you don't want too. If you like REALLY_LONG_CLASS_NAMES that's still perfect
Arvids Godjuks a écrit :
Of course that isn't a good example, because Zend framework always has a
class prefix "Zend", but they surely can use a namespace and remove that
Zend in front of classes.
They are a lot of case where you want to use this syntax. The most
common is when you have a d
I completely agree with jvlad's thoughts - for me namespace is ability to
separate two different libraries from each other so that they don't
conflict. I don't need namespaces just to write my own application using
them to be cool, and I probably would never use a namespace for small or
middle size
Steph Fox wrote:
Lets just let it die. It is un-needed, un-wanted by many, and the end
result seems to be less that optimal, or even a true implementation
of namespaces.
Oddly enough, I agree with Kevin with my heart and soul. But then I hear
the howls of outrage from the Other Side, who campa
Steph...
I think you should not tell me this... =) I already know it and heard
(like you) 5,451,741,709,125 times.
Cya,
On Tue, Sep 23, 2008 at 8:31 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
>> For those that do not understand very well the explanation of jvlad...
>
> Guileherme, you are missing
For those that do not understand very well the explanation of jvlad...
Guileherme, you are missing the point. We'd all like to see PHP 5.3.0 out
there. It has a lot to offer, but namespace support is very obviously
problematic. That's it, that's all.
- Steph
--
PHP Internals - PHP Runtime
For those that do not understand very well the explanation of jvlad...
He's suggesting to change the class struct to be an scope struct, and
have a property that tells if it's a namespace or a class, and reuse
the implementation of class which already works very well.
The nested support is achieve
Lets just let it die. It is un-needed, un-wanted by many, and the end
result seems to be less that optimal, or even a true implementation
of namespaces.
Oddly enough, I agree with Kevin with my heart and soul. But then I hear the
howls of outrage from the Other Side, who campaigned without ruth
[EMAIL PROTECTED]: nothing of technical importance in this email, but it might
make you feel better :-) ... even Stas!]]
Kevin Waterson schreef:
This one time, at band camp, "jvlad" <[EMAIL PROTECTED]> wrote:
everything that jvlad wrote was way too vague for me to understand
so I couldn't pos
lists.php.net
Sent: Tuesday, September 23, 2008 3:57:41 PM
Subject: Re: [PHP-DEV] true namespaces, yet another point of view
This one time, at band camp, "jvlad" <[EMAIL PROTECTED]> wrote:
> May I suggest something in this area?
May I suggest something also.. Lets just let nam
This one time, at band camp, "jvlad" <[EMAIL PROTECTED]> wrote:
> May I suggest something in this area?
May I suggest something also.. Lets just let namespaces die and let
it become a repressed memory as it seems it is more trouble that it
is worth. Seriously.
For 10+ years we have got on just
Hello all,
May I suggest something in this area?
I hope it will resolve some problems related to namespaces and classes
ambiguity.
Let's first take a look at the classes.
In-general they represent two things: scope and data.
Scope is a thing that can't be changed without compiler efforts and con
21 matches
Mail list logo
