Would be nice if somebody could have a look at
https://bugs.php.net/bug.php?id=69180 -- thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, May 28, 2015 at 11:39 AM, Levi Morrison wrote:
> On Thu, May 28, 2015 at 11:38 AM, Levi Morrison wrote:
>> On Thu, May 28, 2015 at 1:06 AM, Stanislav Malyshev
>> wrote:
>>> Hi!
>>>
>>> Since we now allow defining return value types for functions, one can
>>> also create definition for m
Hi Eric,
> -Original Message-
> From: Eric Stenson [mailto:erics...@microsoft.com]
> Sent: Tuesday, May 26, 2015 6:18 PM
> To: Anatol Belski; 'Ferenc Kovacs'; internals-...@lists.php.net
> Cc: internals@lists.php.net
> Subject: RE: [INTERNALS-WIN] Re: [PHP-DEV] Q: What is the Config.w32
>
Hi,
We've just got the answer from the person responsible for the NSAPI related
product management. The SDK on which sapi/nsapi depends won't be available.
Thus, we won't be able to support NSAPI further anymore. I'm going to tag away
sapi/nsapi next days in the same manned it was done for the
Hi Jan
2015-05-28 23:15 GMT+02:00 Jan Ehrhardt :
> Did you actually try it? I tried several variations of inserting
> #include but none worked.
Yes I tried it.
VC11 x86 and VC11 x64 was fine, but with VC14 (both x86 and x64), it
threw me a linker error about _printf being undefined, and the
#in
Kalle Sommer Nielsen in php.internals (Thu, 28 May 2015 23:09:12 +0200):
>Hi Jan
>
>2015-05-28 22:42 GMT+02:00 Jan Ehrhardt :
>> Compilation of even deplister.exe is broken in this compiler with a
>> 'unresolved external symbol _printf'. I created a real simple example of
>> the same error. See the
Hi Jan
2015-05-28 22:42 GMT+02:00 Jan Ehrhardt :
> Compilation of even deplister.exe is broken in this compiler with a
> 'unresolved external symbol _printf'. I created a real simple example of
> the same error. See the following console output:
I patched deplister in master for VC14 (works with
"Anatol Belski" in php.internals (Thu, 28 May 2015 14:16:49 +0200):
>> https://www.apachelounge.com/viewtopic.php?p=30557#30557
>
>Thanks for reporting. How do you build, which deps do you use? What I've
>read on the page you've linked sounds terribly wrong
>
>Jan, please open a bug ticket, we can
Hi,
There are two issues (reported bugs but not really bugs) in json_decode
related to \u escape.
First one is
json_decode('{"\u": 1}');
reported in https://bugs.php.net/bug.php?id=68546
That code result in fatal error due to using malformed property (private
props starting with \0). I don't
Hi Stas,
> -Original Message-
> From: Stanislav Malyshev [mailto:smalys...@gmail.com]
> Sent: Thursday, May 28, 2015 7:59 PM
> To: Uwe Schindler; 'Anatol Belski'; 'Internals'; theta...@php.net
> Subject: Re: [PHP-DEV] RIP: NSAPI SAPI Plugin (unfortunately -> thanks
> Oracle)
>
> Hi!
>
>
Hi!
> But if they show no interest, let NSAPI die :-(
I would say let's set a defined point in time (like, 1 month from now),
by which if we don't hear anything from anybody at Oracle indicating
they have any interest in working with PHP we remove it (we can always
add it back if it changes). Als
On Thu, May 28, 2015 at 11:38 AM, Levi Morrison wrote:
> On Thu, May 28, 2015 at 1:06 AM, Stanislav Malyshev
> wrote:
>> Hi!
>>
>> Since we now allow defining return value types for functions, one can
>> also create definition for magic functions that make no sense, such as
>> __toString() : flo
On Thu, May 28, 2015 at 1:06 AM, Stanislav Malyshev wrote:
> Hi!
>
> Since we now allow defining return value types for functions, one can
> also create definition for magic functions that make no sense, such as
> __toString() : float or __isset() : Closure. I think we should restrict
> such defin
Hi Jan,
> -Original Message-
> From: Jan Ehrhardt [mailto:php...@ehrhardt.nl]
> Sent: Thursday, May 28, 2015 11:06 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] Re: PHP 7.0.0 roadmap
>
> "Anatol Belski" in php.internals (Wed, 27 May 2015 16:01:49 +0200):
> >https://wiki.php.net/to
On Thu, May 28, 2015 at 1:08 PM, Pierre Joye wrote:
>
> On May 28, 2015 1:47 PM, "Dmitry Stogov" wrote:
> >
> > Hi Pierre,
> >
> > It looks like the training process is not a trivial task.
> > It may speedup one apps and slowdown others.
> > In my experiments training with many apps leaded to wo
On May 28, 2015 1:47 PM, "Dmitry Stogov" wrote:
>
> Hi Pierre,
>
> It looks like the training process is not a trivial task.
> It may speedup one apps and slowdown others.
> In my experiments training with many apps leaded to worse results.
>
> I'm trying to identify the optimization patterns that
"Anatol Belski" in php.internals (Wed, 27 May 2015 16:01:49 +0200):
>https://wiki.php.net/todo/php70#timetable
>
>In short:
> - the first alpha is tagged on 2015-06-09
> - the first alpha is coming out on 2015-06-11
> - the 7.0.0 final is planned for 2015-11-12
There is a lot to
2015-05-28 9:23 GMT+02:00 Kalle Sommer Nielsen :
> Hi
[snip]
>
> I only think this sounds reasonable, we already do this for
> __toString(), meaning we can convert a few more errors into
> exceptions. So I can only say +1
> --
> regards,
>
> Kalle Sommer Nielsen
> ka...@php.net
/Mornings, forgot t
Hi!
Since we now allow defining return value types for functions, one can
also create definition for magic functions that make no sense, such as
__toString() : float or __isset() : Closure. I think we should restrict
such definitions - either to types that makes sense or in case of
methods that ar
19 matches
Mail list logo
