Hi Greg,
The patch I posted here:
http://pear.php.net/~greg/ns.element.patch.txt
does exactly what you are talking about. For some reason, some people
find this too difficult to digest. I've already expressed my opinion on
the matter (after all, I did spend almost a week developing the patch
+1, or: "Do, or do not. There is no 'try.'"
- David
On 28.09.2008, at 16:29, Steph Fox wrote:
Hi Greg,
The patch I posted here:
http://pear.php.net/~greg/ns.element.patch.txt
does exactly what you are talking about. For some reason, some
people
find this too difficult to digest. I've
On Mon, Sep 22, 2008 at 08:07:10PM +0400, Dmitry Stogov wrote:
> Yes. Changing :: into any other separator solves the functions/static
> methods and constants ambiguity, but it also breaks intuitive syntax.
Which is more important? Considering there have been threads upon
threads filled with my
Steph Fox wrote:
I don't want to see that whole ns separator debate all over again any
more than you do, but I really don't see a good way to avoid it... sorry.
+1, I second this completely
From someone who *was* using namespaces developing against the 5.3
branch, this is going to happen soon
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
There is a bug in stream_filter_remove() that calls the stream destructor
when it shouldn't. I have included two attachments--one is the patch to
streamsfuncs.c and the other is a test.
Take a look :)
Ilia
Index: streamsfuncs.c
===
hi Ilia!
On Mon, Sep 29, 2008 at 12:48 AM, Ilia Cheishvili
<[EMAIL PROTECTED]> wrote:
> There is a bug in stream_filter_remove() that calls the stream destructor
> when it shouldn't. I have included two attachments--one is the patch to
> streamsfuncs.c and the other is a test.
>
> Take a look :)
Sorry for that! I transposed two characters. The right bug # is 46164.
I'll add the patch to the bug as well.
Ilia
On Sun, Sep 28, 2008 at 4:54 PM, Pierre Joye <[EMAIL PROTECTED]> wrote:
> hi Ilia!
>
> On Mon, Sep 29, 2008 at 12:48 AM, Ilia Cheishvili
> <[EMAIL PROTECTED]> wrote:
> > There is
On Mon, Sep 29, 2008 at 12:57 AM, Ilia Cheishvili
<[EMAIL PROTECTED]> wrote:
> Sorry for that! I transposed two characters. The right bug # is 46164.
> I'll add the patch to the bug as well.
Can you do it as well for your other patches please?
Cheers,
--
Pierre
http://blog.thepimp.net | http:/
No problem, I'm do that right now. I'll follow this process in the future,
too :)
Thanks Pierre!
Ilia
On Sun, Sep 28, 2008 at 4:58 PM, Pierre Joye <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 29, 2008 at 12:57 AM, Ilia Cheishvili
> <[EMAIL PROTECTED]> wrote:
> > Sorry for that! I transposed two c
Daniel Convissor wrote:
> On Mon, Sep 22, 2008 at 08:07:10PM +0400, Dmitry Stogov wrote:
>
>> Yes. Changing :: into any other separator solves the functions/static
>> methods and constants ambiguity, but it also breaks intuitive syntax.
>
> Which is more important? Considering there have been th
Hi,
The second highest vote was :::, but there was strong objection to this
as well from some. The problem, I still believe, is that we are focused
on having the same:::stupid:::operator:::between:::everything.
The truth is that in source files, there is a clear boundary between
namespace defin
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
Maybe just use . as namespace separator.
MyNameSpace.SomeClass::_getInstance()->SomeDBClass->Query();
That will eliminate all resolution problems, it isn't used for anything than
string concatenation, and it's one symbol. It's 100% better than \ and I
think it would be better than ::: or a
Hi,
I think we need string concatenation here and there ;)
Regards,
Stan Vassilev
- Original Message -
From: Arvids Godjuks
To: Stan Vassilev | FM
Cc: PHP Internals List
Sent: Monday, September 29, 2008 9:19 AM
Subject: Re: [PHP-DEV] solving the namespace conflict issue
String concatenation woun't be affected, because you can't concatenate class
definitions like in my example.
To concatenate you should use variables or strings/numbers. So I don't see
any complications with that.
2008/9/29 Stan Vassilev | FM <[EMAIL PROTECTED]>
>
> Hi,
>
> I think we need string
16 matches
Mail list logo