Antony Dovgal wrote:
> Hello Sebastian.
Hello Antony,
> What's the status of this?
> Do you have anything working?
back in February/March when I first posted about this, I discussed this
with Marcus. The conclusion was that we wanted to rewrite run-tests.php
based on the Iterator approach I
On 05.06.2007 11:25, Sebastian Bergmann wrote:
Antony Dovgal wrote:
Hello Sebastian.
Hello Antony,
What's the status of this?
Do you have anything working?
back in February/March when I first posted about this, I discussed this
with Marcus. The conclusion was that we wanted to rewrite r
Antony Dovgal wrote:
On 05.06.2007 11:25, Sebastian Bergmann wrote:
Antony Dovgal wrote:
Hello Sebastian.
Hello Antony,
What's the status of this?
Do you have anything working?
back in February/March when I first posted about this, I discussed this
with Marcus. The conclusion was that
On 05.06.2007 12:22, Lukas Kahwe Smith wrote:
Antony Dovgal wrote:
On 05.06.2007 11:25, Sebastian Bergmann wrote:
Antony Dovgal wrote:
Hello Sebastian.
Hello Antony,
What's the status of this?
Do you have anything working?
back in February/March when I first posted about this, I discus
On 6/5/07, Antony Dovgal <[EMAIL PROTECTED]> wrote:
> Well SPL should not be allowed to be disabled anyways, imho.
I agree, but that's out of the topic.
Well, as we may require for the tests suite, and it looks like a non
sense to be able to disable part of it, it is the right time to fix
sol
On Tue, 5 Jun 2007, Antony Dovgal wrote:
> On 05.06.2007 12:22, Lukas Kahwe Smith wrote:
> > Antony Dovgal wrote:
> > > On 05.06.2007 11:25, Sebastian Bergmann wrote:
> > > > Antony Dovgal wrote:
> > > >
> > > > > What's the status of this?
> > > > > Do you have anything working?
> > > >
> > > >
Hello all.
I'd like to propose a small patch adding two command line switches to CLI
(HEAD):
-U - turn Unicode mode on
-N - turn Unicode mode off
Typing "-d unicode.semantics=1" or "-d unicode.semantics=0" is annoying,
so I would really like to see these shortcuts added.
I'll port it to CGI l
I'd like to say something involving smoke and carcass but that'll bite me later
so.. :)
I'm all for moving the useful stuff to Zend where it belongs.
But I'm totally against making SPL another exception to the rule.
Along with ext/date and ext/standard that is. Extension is an extension.
It's no
On 6/5/07, Antony Dovgal <[EMAIL PROTECTED]> wrote:
Hello all.
I'd like to propose a small patch adding two command line switches to CLI
(HEAD):
Very good idea!
-U - turn Unicode mode on
-N - turn Unicode mode off
What's about:
long: --unicode (0|off)/(1/on)
short: -u (0|off)/(1/on)
I p
Pierre wrote:
It should not be possible to disable it. Or even better, we should
move what we consider as core from SPL to Zend.
Amen.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 05.06.2007 12:43, Derick Rethans wrote:
> > Require SPL for a test suite?
> > Doesn't seem to be good idea..
>
> Well SPL should not be allowed to be disabled anyways, imho.
I agree, but that's out of the topic.
Then what is the issue with using this in the tests suite?
<@tony2001> I kn
Hi all
Would it be possible to have a Bugzilla category for test case bugs?
The only alternative seems to be to raise a bug against the
implementation - which doesn't seem quite right.
Zoe Slattery
IBM
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
Hi,
Hopefully I am not overlooking something here, but I never really
appreciated the fact that all my complex types are returned as stdClass
instances by default. Of course you can override this with custom
classes via the classmap, but I would much prefer simple boring arrays.
This has now
On 6/5/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Hi all
Would it be possible to have a Bugzilla category for test case bugs?
The only alternative seems to be to raise a bug against the
implementation - which doesn't seem quite right.
Why not simply put them in the related category? For examp
Hi Lukas,
I don't like to increase complexity of ext/soap with additional options.
It is already complex enough and simple object <-> array conversion doesn't
provide additional abilities.
I don't understand how ext/soap related to APC.
Thanks. Dmitry.
> -Original Message-
> From: Lukas
Dmitry Stogov wrote:
I don't like to increase complexity of ext/soap with additional options.
It is already complex enough and simple object <-> array conversion doesn't
provide additional abilities.
Well we have way more functions to "play" with arrays than we have with
objects. Considering
> -Original Message-
> From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 05, 2007 4:47 PM
> To: Dmitry Stogov
> Cc: 'PHP Developers Mailing List'
> Subject: Re: [PHP-DEV] RE: using arrays instead of stdClass
>
>
> Dmitry Stogov wrote:
>
> > I don't like to increase
Pierre wrote:
On 6/5/07, Zoe Slattery <[EMAIL PROTECTED]> wrote:
Hi all
Would it be possible to have a Bugzilla category for test case bugs?
The only alternative seems to be to raise a bug against the
implementation - which doesn't seem quite right.
Why not simply put them in the related cate
Bart de Boer wrote:
> Ken Stanley wrote:
>
...
> That's not right. Accessing the child class would only be possible from
> within an instantiated object. Unlike parent::, you will never be able
> to use static:: in a purely static context. Imagine there are multiple
> child classes which all inh
Jochem Maas wrote:
Bart de Boer wrote:
Ken Stanley wrote:
...
That's not right. Accessing the child class would only be possible from
within an instantiated object. Unlike parent::, you will never be able
to use static:: in a purely static context. Imagine there are multiple
chil
> Bart de Boer wrote:
>> Ken Stanley wrote:
>>
>
> ...
>> That's not right. Accessing the child class would only be possible from
>> within an instantiated object. Unlike parent::, you will never be able
>> to use static:: in a purely static context. Imagine there are multiple
>> child classes whi
Bart de Boer wrote:
I thought late static binding had something to do with accessing static
_variables_ in child classes. You're currently solving that problem by
defining a static function getTableName() in the child class. But I think
that isn't very efficient when you're dealing with complex o
Well the problem is that I am trying to cache soap replies in APC. This
seems to be buggy but at the very least will require a
serialize/unserialize call, which again adds overhead.
Wouldn't array require serializing too? Or APC is able to store arrays
in unserialized form? Anyway you could us
Etienne Kneuss wrote:
It's always dangerous to introduce a new keyword, as it can/will break
BC (i.e what if somebody has defined a function derived(), the parser
would choke on that).
I'm personally fine with static, even if it may eventually introduce
some confusion.
Regards
Perhap
Hi Wez,
We really need an update to the [EMAIL PROTECTED] alias. This is the
4th request. Please remove [EMAIL PROTECTED] and add [EMAIL PROTECTED]
Thanks,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
It's done (1 insert, 1 delete).
- Sascha
On Tue, 5 Jun 2007, Greg Beaver wrote:
> Hi Wez,
>
> We really need an update to the [EMAIL PROTECTED] alias. This is the
> 4th request. Please remove [EMAIL PROTECTED] and add [EMAIL PROTECTED]
>
> Thanks,
> Greg
>
>
--
PHP Internals - PH
Hello,
On 6/5/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
Hello internals,
let's make ext/pcre and ext/spl first class core components and not allow
to disable them.
I fail to see what:
class_implements
class_parents
iterator_count
iterator_to_array
spl_autoload_cal
spl_autoload_extensi
Hello internals,
let's make ext/pcre and ext/spl first class core components and not allow
to disable them.
SPL:
+ influences a bunch of other stuff, and some extensions even behave
different whether SPL is shared or built-in, this is hard to realize
and understand for our users
+
let's make ext/pcre and ext/spl first class core components and not allow
to disable them.
Well, theoretically I can imagine reason why somebody would like to
disable them - e.g., if I need super-high-performance server and I
absolutely must squeeze out every last bit of cpu/memory usage _
On 6/5/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
I might want to disable it.
In any case, I see the reasons why we *want* it enabled. But I'd like to
hear any reasons why we *need* it enabled - i.e. any vital stuff that
can't work with SPL/PCRE disabled?
I just listed two:
- the array
Stanislav Malyshev wrote:
Well, theoretically I can imagine reason why somebody would like to
disable them - e.g., if I need super-high-performance server and I
absolutely must squeeze out every last bit of cpu/memory usage _and_ I
don't do neither SPL nor regular expressions - I might want to
Dear internals,
I stumbled upon the following odd error message from PHP which I was not
expecting.
Here is a small example that triggered the error with 5.2.2, 5.2.3 and a
php5.2-200706052030 snapshot.
c2 = $c2;
}
}
class class2{
public $c1;
function setC1($c1){
$this->c1 = $c1;
}
- the array bugs in object properties. There is no other work around
but to use ArrayObject. And this is rather critical.
Could you elaborate - which bugs?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/
--
PHP Internals - PHP Runtime Development Mailing L
On 6/5/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> - the array bugs in object properties. There is no other work around
> but to use ArrayObject. And this is rather critical.
Could you elaborate - which bugs?
A rude explanation was here:
http://blog.thepimp.net/index.php/post/2006/11/
Hello Pierre,
Tuesday, June 5, 2007, 10:36:54 PM, you wrote:
> Hello,
> On 6/5/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>> Hello internals,
>>
>> let's make ext/pcre and ext/spl first class core components and not allow
>> to disable them.
> I fail to see what:
> class_implements
> cla
On 06.06.2007 01:10, [EMAIL PROTECTED] wrote:
c2 = $c2;
}
}
class class2{
public $c1;
function setC1($c1){
$this->c1 = $c1;
}
function test(){
echo $this == $this->c1->c2?'equals':'not equals'; // Somehow this
if statement triggers the error.
}
}
$tt = new class2();
$t =
Hello,
On 6/5/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
I sniped the rest as we can argue endlessly about what should be in or
out, I think I made my point :)
However, in case I did not make it, here it is:
Just a standard OOP function. Nothign that belongs into the engine.
If it is sta
Could you elaborate - which bugs?
A rude explanation was here:
http://blog.thepimp.net/index.php/post/2006/11/28/comment-posting-fixed-and-warning-removed-and-some-overload-mess
I'm not sure I understand where is the bug. If your __get doesn't return
by reference, it can't be modified. That
On Tue, June 5, 2007 3:19 pm, Marcus Boerger wrote:
> let's make ext/pcre and ext/spl first class core components and not
> allow
> to disable them.
PCRE: +0.5
SPL: -1 (Just confuses me, never use it, don't need it)
ymmv
imho
.
.
.
--
Some people have a "gift" link here.
Know what I want?
I
On Tue, June 5, 2007 4:10 pm, [EMAIL PROTECTED] wrote:
> Dear internals,
>
> I stumbled upon the following odd error message from PHP which I was
> not
> expecting.
>
> Here is a small example that triggered the error with 5.2.2, 5.2.3 and
> a
> php5.2-200706052030 snapshot.
>
> class class1{
>
Hello Pierre,
Tuesday, June 5, 2007, 11:21:48 PM, you wrote:
> Hello,
> On 6/5/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> I sniped the rest as we can argue endlessly about what should be in or
> out, I think I made my point
> However, in case I did not make it, here it is:
>> Just a st
People judge your dick size by your shoes size.
With megadik you dont have to wear
bigger shoes to make women think you have a huge dick.
You can actually have it. http://brazty.com/
1867 - U.S. Secretary of State William H. Seward
Unlike television programming, most radio listeners use
order to f
On Tue, Jun 05, 2007 at 23:15:22 +0200, Pierre wrote:
> On 6/5/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> >> - the array bugs in object properties. There is no other work around
> >> but to use ArrayObject. And this is rather critical.
> >
> >Could you elaborate - which bugs?
>
> A rude e
The big reason for PCRE is the fact that other, rather important
extensions such as filter depend on it. SPL is also used by other
extensions, which could be a "need" reason.
On 5-Jun-07, at 4:58 PM, Stanislav Malyshev wrote:
let's make ext/pcre and ext/spl first class core components and
[EMAIL PROTECTED] wrote:
> Dear internals,
>
> I stumbled upon the following odd error message from PHP which I was not
> expecting.
> function test(){
> echo $this == $this->c1->c2?'equals':'not equals'; // Somehow this
Use === (shallow test - returns true iff the variables refer to the sam
Antony Dovgal wrote:
On 06.06.2007 01:10, [EMAIL PROTECTED] wrote:
c2 = $c2;
}
}
class class2{
public $c1;
function setC1($c1){
$this->c1 = $c1;
}
function test(){
echo $this == $this->c1->c2?'equals':'not equals'; // Somehow
this if statement triggers the error.
}
}
$tt
The big reason for PCRE is the fact that other, rather important
extensions such as filter depend on it. SPL is also used by other
extensions, which could be a "need" reason.
But you can run PHP without filter extension.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://w
Paweł Stradomski wrote:
[EMAIL PROTECTED] wrote:
Dear internals,
I stumbled upon the following odd error message from PHP which I was not
expecting.
function test(){
echo $this == $this->c1->c2?'equals':'not equals'; // Somehow this
Use === (shallow test - returns true iff the v
On 6/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Paweł Stradomski wrote:
> [EMAIL PROTECTED] wrote:
>
>> Dear internals,
>>
>> I stumbled upon the following odd error message from PHP which I was not
>> expecting.
>> function test(){
>> echo $this == $this->c1->c2?'equals':'not equal
On 06.06.2007 02:20, [EMAIL PROTECTED] wrote:
Fatal error: Nesting level too deep - recursive dependency? in
/home/cyanox/DEV/test_object_recursion.php on line 15
$t->$tt->$t->$tt->$t->$tt->$t->$tt->$t->$tt->$t and so on.
So you get endless recursion when comparing the objects.
Although it is
50 matches
Mail list logo
