Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions are deprecated and emit E_DEPRECATED errors.
Use PCRE (preg_*()) instead.
... is accurate, I think a little more detail would help here, since
many of us probably did
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions are deprecated and emit E_DEPRECATED errors.
Use PCRE (preg_*()) instead.
... is accurate, I think a little more detail
Lukas Kahwe Smith wrote:
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions are deprecated and emit E_DEPRECATED errors.
Use PCRE (preg_*()) instead.
... is accurate, I
On 21.06.2009, at 10:24, Lester Caine wrote:
Lukas Kahwe Smith wrote:
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions are deprecated and emit E_DEPRECATED errors.
Use
On 21.06.2009, at 10:29, Lukas Kahwe Smith wrote:
On 21.06.2009, at 10:24, Lester Caine wrote:
Lukas Kahwe Smith wrote:
On 21.06.2009, at 09:51, Lester Caine wrote:
Johannes Schlüter wrote:
On Sat, 2009-06-20 at 07:49 +0100, Lester Caine wrote:
While I know that ...
- All ereg functions
Hi
Guys and gals, in the old days we had a very close tie between the code
and the documentation. As the project has grown the two have drifted
apart. I think this is mostly because the phpdoc team has done an
amazing job keeping up with the code changes and writing awesome
documentation.
I ran the entire PHP testsuite (as compiled on my system) under
valgrind for Darwin and came up with quite a mess of leaks and a
couple of crashes.
The results file is quite ginormous, so I uploaded it to my site for
the morbidly curious to have a look at:
Lukas Kahwe Smith wrote:
There is a reason why E_DEPRECATED isn't part of E_ALL. Anyways, its
your call, but its not what we suggest. But overall there is always
room for doc improvements (feel free to help out), but in the end you
need to know the code or familiarize yourself with the code if
2009/6/19 Rasmus Lerdorf ras...@lerdorf.com:
Guys and gals, in the old days we had a very close tie between the code
and the documentation. As the project has grown the two have drifted
apart. I think this is mostly because the phpdoc team has done an
amazing job keeping up with the code
On Jun 21, 2009, at 6:23 AM, zoe wrote:
Guys and gals, in the old days we had a very close tie between the
code
and the documentation. As the project has grown the two have drifted
apart. I think this is mostly because the phpdoc team has done an
amazing job keeping up with the code changes
Gwynne Raskind wrote:
On Jun 21, 2009, at 6:23 AM, zoe wrote:
Guys and gals, in the old days we had a very close tie between the code
and the documentation. As the project has grown the two have drifted
apart. I think this is mostly because the phpdoc team has done an
amazing job keeping up
Hi Georg,
I notice this commit that looks like a benchmark. I'm trying to figure
out if the new run-tests rewrite overlaps with the benchmarks GSoC
project (you might not have been aware since we have the discussions
on php-qa). I wouldn't mind hearing your thoughts so that we avoid
duplicated
Hi Paul,
thanks for the notice. To cut a long story short: we've discussed the use of
the SPL-File-Iterator in the runtests-project. So I created a very simple
test which passes through an array to compare the performance of the
spl-iterator to a for-loop.
So I think this is no overlap with
Hi Georg,
Thanks for the quick reply.
On Sun, Jun 21, 2009 at 8:22 PM, Georg Gradwohlgeorg.gradw...@gmail.com wrote:
thanks for the notice. To cut a long story short: we've discussed the use of
the SPL-File-Iterator in the runtests-project. So I created a very simple
test which passes through
Hi,
It looks like nothing critical has popped up since RC4.
So it looks like we will be sending the final stable release to the
mirrors next Wednesday and announce the release on Thursday barring
any critical issues emerging in the next days. In the mean time test
test test. If issues are
Hi,
It looks like nothing critical has popped up since RC4.
So it looks like we will be sending the final stable release to the
mirrors next Wednesday and announce the release on Thursday barring any
critical issues emerging in the next days. In the mean time test test
test. If issues
16 matches
Mail list logo
