On Sat, Jul 19, 2014 at 4:15 AM, Yasuo Ohgaki wrote:
> Hi all,
>
> On Wed, Jul 16, 2014 at 9:46 AM, Yasuo Ohgaki wrote:
>
> > crypt() has BC issue with older systems.
> >
> > https://bugs.php.net/bug.php?id=62372&edit=1
> >
> > The reason rounds became 1000 from 10 is hardcoded lower limit for n
Hi all,
On Wed, Jul 16, 2014 at 9:46 AM, Yasuo Ohgaki wrote:
> crypt() has BC issue with older systems.
>
> https://bugs.php.net/bug.php?id=62372&edit=1
>
> The reason rounds became 1000 from 10 is hardcoded lower limit for newer
> PHPs.
> Generally speaking, developer should never use less than
Hi Anthony,
On Fri, Jul 18, 2014 at 6:56 AM, Anthony Ferrara
wrote:
> > Anthony, do you have suggestion for removing 72 char restriction of
> > PASSWORD_BCRYPT?
>
> My suggestion is to leave it there (it's no longer bcrypt if you do
> something to remove it). Here's a deeper explanation:
> http:
>> Another concern I have is in regard to the future. I'm looking
>> forward to the possibility of specifying nullable types in a
>> future version of PHP (see Levi Morrison's "Declaring Nullable
>> Types" RFC: http://wiki.php.net/rfc/nullable_typehints). If the
>> nullable types RFC is accepted, i
On 18 Jul 2014, at 12:31, Jon Arano wrote:
>>
Were you meaning to say something?
--
Andrea Faulds
http://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 18 Jul 2014, at 06:02, Theodore Brown wrote:
> Another concern I have is in regard to the future. I'm looking forward to the
> possibility of specifying nullable types in a future version of PHP (see Levi
> Morrison's "Declaring Nullable Types" RFC:
> http://wiki.php.net/rfc/nullable_typeh
On 18 Jul 2014, at 04:39, Tjerk Meesters wrote:
> This makes it more complicated because a language change requires 2/3
> majority while a new function requires 50% + 1.
>
> To make things simpler - and I believe it had been proposed before - the
> main vote should include the implementation as
On 27 June 2014 06:12, Stas Malyshev wrote:
> Hello!
>
> The PHP development team announces the immediate availability of PHP
> 5.4.30. Over 20 bugs were fixed in this release, including the following
> security issues: CVE-2014-3981, CVE-2014-0207, CVE-2014-3478,
> CVE-2014-3479, CVE-2014-3480,
Hi,
can anyone shed a light on what zend_stream_fixup (in zend_stream.c) is for?
>From what I get from the code, it seems it ensures that the whole file
is read into memory, no matter what type the zend_file_handle is...
Thanks!
Greetings
Nico
--
PHP Internals - PHP Runtime Development Maili
On Fri, Jul 18, 2014 at 7:02 AM, Theodore Brown wrote:
>> Since I am very much in favour of scalar type hints, I've updated the
>> patch to master and made some minor improvements, and I am re-opening
>> the RFC with the intent to try and get it into PHP 5.7.
>
> First of all, this is my first rep
bump.
On Tue, Jul 8, 2014 at 5:48 PM, Ferenc Kovacs wrote:
>
>
>
> On Sat, Jun 14, 2014 at 2:45 PM, Johannes Schlüter > wrote:
>
>> Hi,
>>
>> On Fri, 2014-06-13 at 16:38 -0700, Stas Malyshev wrote:
>> > As decided in https://wiki.php.net/rfc/php53eol, 5.3 EOL is 1 year
>> after
>> > the 5.5.0
11 matches
Mail list logo