Hello php experts,
We are doing php upgrade from 5.2.3 to 5.3.2 (unix on Octeon/MIPS) and getting
a compilation error
* Issue with Octeon platform
o Round() API throws "Maximum execution time exceeded" error. Analyzed
the issue and Found the problem to be that "mult" function
(src
Patrick Reilly prei...@php.net asked me to fill it out. He wants me to take
over evangelism efforts.
- Patrick
On Thu, May 6, 2010 at 1:56 PM, Hannes Magnusson wrote:
> On Thu, May 6, 2010 at 23:04, Robert Chu wrote:
> > Manage this group instead of Patrick Reilly.
> > http://news.php.net/grou
On Thu, May 6, 2010 at 23:04, Robert Chu wrote:
> Manage this group instead of Patrick Reilly.
> http://news.php.net/group.php?group=php.evangelism
huh?
You don't need SVN account to sign up to the mailinglist..
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
Manage this group instead of Patrick Reilly.
http://news.php.net/group.php?group=php.evangelism
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Felipe:
Hope you don't mind that I post it on the list, think the discussion should be
properly archived.
On 06 May 2010, at 18:30, Felipe Pena wrote:
> Hello,
>
> 2010/5/6 Stefan Marr
> Hi Felipe:
>
> On 05 May 2010, at 22:00, Felipe Pena wrote:
> > One question... Looking at the gramm
I am referring to the SQLite version that is bundled in PDO-SQLite in
PHP 5.2. That is the one I have been using in my PHP builds.
I am suggesting that the version numbers reported by the VERSION file
and the phpinfo() function are misleading.
- Ken
On Thu, May 6, 2010 at 12:43 PM, Pierre Joye
hi,
Do you build php against an external version?
Cheers,
On Thu, May 6, 2010 at 7:48 PM, Ken Dreyer wrote:
> In PHP 5.2, phpinfo() reports the PDO-SQLite version as "3.3.7".
> However, from the SVN history of the 5.2 branch, SQLite 3.3.15 and
> even part of 3.3.16 were merged in. The VERSION f
hi,
I like the feature, it is a nice and useful one.
However nobody ever posted anything on internals about it. The
differences between the implementation and the RFC as well as the
questions raised by this addition show that it would be better to
discuss prior to commit.
But as it is in trunk,
In PHP 5.2, phpinfo() reports the PDO-SQLite version as "3.3.7".
However, from the SVN history of the 5.2 branch, SQLite 3.3.15 and
even part of 3.3.16 were merged in. The VERSION file was updated to
track this, but someone changed it to "3.3.7" under the assumption
that "3.3.17" was a typo.
http:
PS: Argh, sorry... pressed the send button without finishing to write the email.
Consistency that matches with Serializable interface when dealing with
(un)serialize(). So if we have to vote, I'd go for Jsonable.
The method should be renamed to _toJSON (I can even accept __toJson
here), using the
Hi guys,
I'd like to thank you for this implementation.
@Pierre: There is a RFC I wrote: http://wiki.php.net/rfc/jsonable
I'd suggest to rather be JSONSerializable or be Jsonable.
JSON is an acronym, the same as PDO. We don't have interface for Pdo,
but for PDO.
So we should keep consistency.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 06.05.10 14:55, schrieb Frederic Hardy:
> Hello !
>
> I don't known why the dtrace version has a relation with the fact that
> the file zend_dtrace_gen.h is not in the trunk...
> Perhaps you can explain that to me ?
zend_dtrace_gen.h is generated d
Hello !
I don't known why the dtrace version has a relation with the fact that
the file zend_dtrace_gen.h is not in the trunk...
Perhaps you can explain that to me ?
error: zend_dtrace_gen.h: No suchfile or directory
Best regards,
Fred.
--
PHP Internals - PHP Runtime Development Mailing Lis
On 31.03.2010, at 07:22, Rasmus Lerdorf wrote:
> On 03/30/2010 08:41 PM, Philip Olson wrote:
>>
>> It's awesome that PHP has so many great options for the next Release Manager
>> because all of the proposed people would do great. However, I'd like to see
>> Rasmus become RM. Not sure about the
On 06.05.2010 15:21, David Soria Parra wrote:
> FreeBSD Dtrace is known to be broken because of a syntax issue somewhere
> in their DTrace scripts that are included by default. FreeBSD dtrace is
> not supported at the moment.
Anyway, you need to check the result of dtrace execution and abort with
On Thu, May 6, 2010 at 12:59 PM, Hannes Magnusson
wrote:
> On Thu, May 6, 2010 at 00:48, Sara Golemon wrote:
>> pollita Wed, 05 May 2010 22:48:14 +
>>
>> Revision: http://svn.php.net/viewvc?view=revision&revision=299037
>>
>> Log:
>> Add JSON_Serializable inte
FreeBSD Dtrace is known to be broken because of a syntax issue somewhere
in their DTrace scripts that are included by default. FreeBSD dtrace is
not supported at the moment.
David
On 2010-05-06, Frederic Hardy wrote:
> Hello !
>
> I'm currently trying to compile the trunk with dtrace under FreeB
Hello !
I'm currently trying to compile the trunk with dtrace under FreeBSD 8
with revision 298979 and i have the following problem :
# ./buildconf
# ./configure --enable-dtrace
#make
...
local/include -g -O2 -fvisibility=hidden -c
/usr/home/fch/php/TSRM/tsrm_strtok_r.c -o TSRM/tsrm_strtok_r
Maybe this one?
http://www.php-security.org/2010/05/03/mops-2010-006-php-addcslashes-interruption-information-leak-vulnerability/index.html
Tyrael
On Wed, May 5, 2010 at 1:26 PM, Mark Skilbeck wrote:
> What exploits are there for __toString()? Just wondering.
>
>
> On 05/05/2010 07:50, Dmitry S
On 5 May 2010 17:25, Richard Quadling wrote:
> Hi.
>
> I'm in the process of getting the PHPDoc classes showing the correct
> inherited properties and methods (public/protected but not private).
>
> I picked RecursiveRegexIterator (it has the largest number of
> xi:includes in the documentation) a
20 matches
Mail list logo
