hi,
On Fri, Dec 12, 2014 at 2:38 AM, Thomas Hruska wrote:
> On 12/11/2014 3:10 AM, Derick Rethans wrote:
>>
>> On Wed, 10 Dec 2014, Andrea Faulds wrote:
>>
On 10 Dec 2014, at 06:33, Remi Collet wrote:
Having a dead upstream for crypto API is a critical issue :(
FYI some
Alain Williams wrote:
> I am updating a PHP course that I occasionally teach ...
>
> Null Coalesce Operator ( ?? )
> What are the precedence and associativity ?
>
> https://wiki.php.net/rfc/isset_ternary
According to master[1] it's right associative and the precendence is
between ?: and ||.
I am updating a PHP course that I occasionally teach ...
Null Coalesce Operator ( ?? )
What are the precedence and associativity ?
https://wiki.php.net/rfc/isset_ternary
TIA
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT
Lecturer.
+44 (0) 787
On 11/12/14 20:44, Leigh wrote:
I actually think a generic random bytes function outside of any
cryptographic extensions would be a good idea. Even mcrypt seems like
overkill if all you want is random strings.
mcrypt_create_iv should be left as an alias to that function, even if no mcrypt
exten
Hi!
> Connection pooling could be a good usage of this if we manage to get
> this working again.
Connection pooling is persisting external resources, usually, which can
be done with little regard to zvals, since zval for resource is just a
container holding an opaque pointer. A number of extensio
Hi all,
I am developing a program analysis tool as a PHP extension. The extension
makes use of the zend_set_user_opcode_handler API in order to propagate
information about the variables along the execution.
I have two questions:
1. From my undestanding we can only pre-hook the execution of an opc
On 02/12/2014 22:44, Andrea Faulds wrote:
I’m putting the ZPP Failure on Overflow RFC to a vote. This RFC is an important
prerequisite to the Big Integer Support RFC, as it ensures safety in implicit
integer parameter conversions.
The RFC requires a 2/3 majority, and voting starts today (2014-
On 11 December 2014 at 15:38, Thomas Hruska wrote:
>
> To date, there still isn't a way to access CryptGenRandom() from userland
> without an extension. Access to that Windows function depends on an
> extension to expose php_win32_get_random_bytes() to userland.
> mcrypt_create_iv() and openssl_r
IIRC, we used to support that back in ~2000s, but it got removed based on
the lack of usage and poor implementation.
Connection pooling could be a good usage of this if we manage to get this
working again.
[]s,
On Thu, Dec 11, 2014 at 1:46 PM, Marc Bennewitz wrote:
>
> Am 10.12.2014 um 09:53 s
Am 10.12.2014 um 09:53 schrieb Stanislav Malyshev:
Hi!
Why?
There is a reference counter, which should be increased on put a value
into persistence and on removing a value from persistence decrease it.
So the GC could handle unreferenced zvals.
Because memory which is allocated by the engine
guilhermebla...@gmail.com wrote on 11/12/2014 15:57:
Not trying to demerit the proposal, but accepting ?-> and black magic just
seems wrong, very wrong.
You need to write defensive code, not rely on the language to do that for
you.
But surely if you're consciously deciding to use this feature,
Hi,
Not trying to demerit the proposal, but accepting ?-> and black magic just
seems wrong, very wrong.
You need to write defensive code, not rely on the language to do that for
you.
[]s,
On Thu, Dec 11, 2014 at 2:35 AM, Stanislav Malyshev
wrote:
> Hi!
>
> > First, how is this substantially di
On 12/11/2014 3:10 AM, Derick Rethans wrote:
On Wed, 10 Dec 2014, Andrea Faulds wrote:
On 10 Dec 2014, at 06:33, Remi Collet wrote:
Having a dead upstream for crypto API is a critical issue :(
FYI some downstream (ex RHEL) don't even provide this library.
Already too much crypto libraries, a
I need a christmas holiday project, I'll look into a
php7-mcrypt-compat ext backed by OpenSSL then, and see what is
possible and what is not.
I've actually found OpenSSL to be much faster than mcrypt in practice,
so hopefully we can get a performance boost out of this too.
P.S. https://github.com
On 11 December 2014 at 07:52, Sebastian Bergmann wrote:
> Hi!
>
> I just updated my notebook to Fedora 21 and am no longer able to
> build PHP on it since I now have bison 3.0.2 instead of bison 2.7.
>
> bison 3.0 is blacklisted in Zend/acinclude.m4. Is bison 3.0
> incompatible with our parse
Hi,
On Wed, December 10, 2014 16:27, Dmitry Stogov wrote:
> Hi,
>
>
> Please, review the following patch
> https://gist.github.com/dstogov/fba2cc621ef121826efe
>
>
> It's huge, but actually, only changes in zend_compile.h are matter. The
> rest is obvious renaming.
>
> the main idea - the smaller
Right. Actually ZEND_EX_USE_RUN_TIME_CACHE and ZEND_EX_USE_LITERALS just
control if corresponding fields of executed op_array should be cached in
current call frame (zend_execute_data). VM will have to execute additional
read/write on enter to each function, but then safe 1 read on each access
to r
On Wed, 10 Dec 2014, Andrea Faulds wrote:
> > On 10 Dec 2014, at 06:33, Remi Collet wrote:
> >
> > Having a dead upstream for crypto API is a critical issue :(
> >
> > FYI some downstream (ex RHEL) don't even provide this library.
> > Already too much crypto libraries, and it will be a mess to
Hi,
2014-12-10 16:27 GMT+01:00 Dmitry Stogov :
> Hi,
>
> Please, review the following patch
> https://gist.github.com/dstogov/fba2cc621ef121826efe
Looks good, but Isn't ZEND_EX_USE_RUN_TIME_CACHE always defined to 1
with your patch?
Regards,
Patrick
--
PHP Internals - PHP Runtime Development M
AFAIK, PHP builds fine with bison 3. At least with the common scenarios on
UNIX like systems.
TS builds might be the problem if my memory serves me right.
Kaplan
On Thu, Dec 11, 2014 at 9:36 AM, Ferenc Kovacs wrote:
> On Thu, Dec 11, 2014 at 8:52 AM, Sebastian Bergmann
> wrote:
>
> > Hi!
> >
On Fri, Dec 5, 2014 at 2:01 AM, Benjamin Eberlei wrote:
>
> I agree, this change makes sense this way and is compatible to the way
> hooks work right now. This change can be part of the grand refactoring
> later on.
7.0 is indeed the best time to do it.
> Refactoring the whole extension API is
On Thu, Dec 11, 2014 at 8:52 AM, Sebastian Bergmann
wrote:
> Hi!
>
> I just updated my notebook to Fedora 21 and am no longer able to
> build PHP on it since I now have bison 3.0.2 instead of bison 2.7.
>
> bison 3.0 is blacklisted in Zend/acinclude.m4. Is bison 3.0
> incompatible with our p
Hi,
Le 11 déc. 2014 09:08, "Sebastian Bergmann" a écrit :
>
> $ git status
> On branch PHP-5.6
> Your branch is up-to-date with 'origin/PHP-5.6'.
> nothing to commit, working directory clean
>
> $ ./configure --disable-all
> .
> .
> .
> Thank you for using PHP.
>
> config.status: error:
$ git status
On branch PHP-5.6
Your branch is up-to-date with 'origin/PHP-5.6'.
nothing to commit, working directory clean
$ ./configure --disable-all
.
.
.
Thank you for using PHP.
config.status: error: cannot find input file: `php7.spec.in'
$ git status
On branch PHP-5.6
Your bran
24 matches
Mail list logo
