روزها در گذر زمان به محرم مي رسند به ماهي متفاوت از همه ماههايي که هر سال تجربه
کرده ايم و مي کنيم. ماهي که ديرگاهي است دلها و ذهن هاي فراواني را به خود مشغول
داشته است و باعث آفرينش ها شده است
صد ها سال از آن واقعه عظيم مي گذرد و ميليونها انسان دلبستگي خود به محرم را به
شکل هايي متفاوت نشان داد
Yes, we should not mask the exception. The behavior in 7.0/7.1.0RC1 is much
better IMO.
(As seen here: https://3v4l.org/EJpD4#v700)
- Davey
On Fri, Oct 7, 2016 at 12:52 PM, Nikita Popov wrote:
> On Fri, Oct 7, 2016 at 9:31 PM, Derick Rethans wrote:
>
> > Hi,
> >
> > I was looking at Xdebug fo
On Fri, Oct 7, 2016 at 9:31 PM, Derick Rethans wrote:
> Hi,
>
> I was looking at Xdebug for PHP 7.1, and I ran into the following
> inconsistency:
>
> https://3v4l.org/tHteN
>
> I first thought that Xdebug was messing up, but it seems like it's
> different behaviour in PHP itself. As I clearly re
Hi,
I was looking at Xdebug for PHP 7.1, and I ran into the following
inconsistency:
https://3v4l.org/tHteN
I first thought that Xdebug was messing up, but it seems like it's
different behaviour in PHP itself. As I clearly return an array from
__debugInfo, I don't think the new result is the
I'd suggest URL to be immutable and have a URLBuilder (obtainable through
URL::createBuilder()) for that...
On Fri, Oct 7, 2016 at 10:45 AM, David Walker wrote:
> Hi Nikita,
>
> On Fri, Oct 7, 2016 at 4:37 AM Nikita Popov wrote:
>
> > Are you aware of the WHATWG URL standard [1]? Quoting the fi
Hi Nikita,
On Fri, Oct 7, 2016 at 4:37 AM Nikita Popov wrote:
> Are you aware of the WHATWG URL standard [1]? Quoting the first goal
> statement:
>
> > Align RFC 3986 and RFC 3987 with contemporary implementations and
> obsolete them in the process. (E.g., spaces, other "illegal" code points,
>
On Fri, Oct 7, 2016 at 2:22 PM, Stephen Reay wrote:
> I think adopting the JavaScript model here is not an improvement.
>
> One of the strengths of parse_url is that it can parse a partial url and
> give the parts that are found. How do we achieve the same using the whatwg
> concept where relativ
2016-10-07 12:55 GMT+02:00 Yasuo Ohgaki :
> Hi Michal,
>
> On Fri, Oct 7, 2016 at 6:47 PM, Michał Brzuchalski
> wrote:
> > 2016-10-07 11:21 GMT+02:00 Michał Brzuchalski :
> >
> >> How about complete rewrite with OOP? It could be implemented using
> Objects
> >> like DateTime does.
> >> I've got w
Results for project PHP master, build date 2016-10-07 06:24:42+03:00
commit: 432e16c
previous commit:1e986c7
revision date: 2016-10-07 01:13:49+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Hi Michal,
On Fri, Oct 7, 2016 at 6:47 PM, Michał Brzuchalski
wrote:
> 2016-10-07 11:21 GMT+02:00 Michał Brzuchalski :
>
>> How about complete rewrite with OOP? It could be implemented using Objects
>> like DateTime does.
>> I've got working implementation in userland https://github.com/madkom/ur
On Tue, Oct 4, 2016 at 8:14 PM, David Walker wrote:
> Hi all,
>
> A couple weeks back I took a look at 72811[1]. The bug being that
> parse_url() didn't accept IPv6 addresses without a scheme, like it did for
> IPv4 addresses. I attempted to patch the specific bug within the scope of
> how pars
2016-10-07 11:21 GMT+02:00 Michał Brzuchalski :
> How about complete rewrite with OOP? It could be implemented using Objects
> like DateTime does.
> I've got working implementation in userland https://github.com/madkom/uri it
> maybe not be finished yet but supports parsing URI with IPv4, IPv6 and
How about complete rewrite with OOP? It could be implemented using Objects
like DateTime does.
I've got working implementation in userland https://github.com/madkom/uri it
maybe not be finished yet but supports parsing URI with IPv4, IPv6 and
Hostnames.
It was also going to parse query arguments fr
13 matches
Mail list logo
