>From the RFC:
> var is therefore a limited subset of public.
No, this is wrong. `var` was here much much longer than `public`, therefore
`var` is not a subset of public, but rather `public` is _an extension_ of
`var`. The keyword `var` is also unique for it's semantics in the later
versions of
Hi Midori,
what about targetting this to the next PHP 7.x?
--
Kubis
On 10-Mar-2016 12:11 am, "Ryan Pallas" wrote:
> On Wed, Mar 9, 2016 at 11:14 AM, Midori Kocak wrote:
>
> > Hi all,
> >
> > Remember my question about ??= operator?
> >
> > Forgive my rookieness and let me introduce my first RF
On 29 February 2016 at 15:25, Tony Marston wrote:
> If "var" is automatically translated into "public", and has been since PHP 5
> emerged, and has been documented to behave in this way, then what does it
> cost to leave it that way? Answer: NOTHING!
Yeah. This is actually very true.
--
Cheers
Good morning Internals!
I am strongly AGAINST the removal of the `var` keyword from PHP
syntax. Though in general it's an alias of `public` (or it simply
‘acts’ as the `public` modifier), I see a difference in its
_semantics_. While the `public` modifier states anyone can change the
property, `var
Dear internals!
I have encountered an inconsistence, or rather a bug, in PHP's syntax.
The thing is, in PHP you can access constants defined on a
class using reference to an instance of this class, stored in
variable. So we have a code:
Which will nicely pass. But things will go wrong having a
everyone's own, but for me it's the first. However, it
couldn't be a disaster having ability to choose other option for
those, who are not familiar with relative paths. :-)
Best regards,
Kubo2, Jakub Kubíček
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
default -- it can
not work work properly without having this extension available.
I say +1 for raising a E_ERROR on random_int()/random_bytes() fail.
Best regards,
Kubo2, Jakub Kubíček
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1 for everything proposed here :-)
Kubo2
2015-07-02 9:59 GMT+02:00 Dmitry Stogov :
> On Thu, Jul 2, 2015 at 3:26 AM, Bob Weinand wrote:
>
>> > Am 29.06.2015 um 19:14 schrieb Andrea Faulds :
>> >
>> > Hi again,
>> >
>> >> On 29 Jun 2015, at 18:02, Bob Weinand wrote:
>> >>
>> >> Yes, it genera
make the HTML code more readable and
self-explainable).
I would argue that software can be updated, but... okay, let it be.
Best regards,
Kubo2, Jakub Kubíček
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1 for allowing trailing comma in every function call.
Regards,
Kubo2
2015-06-18 19:16 GMT+02:00 Florian Anderiasch :
> On 18.06.2015 08:25, Yasuo Ohgaki wrote:
>>> If people still consider it more harm- than useful then please don't flame
>>> me and I'll shut up again :-)
>>>
>>
>> PHP allows
re
the first beta is released if I wanna include it in PHP7 or rather to
target it against PHP 7.1.
Thanks for your reply.
Best regards
Kubo2, Jakub Kubíček
2015-06-25 17:03 GMT+02:00 Kalle Sommer Nielsen :
> Howdy
>
> This is a quick heads up that we plan to have the next release of
&g
2015-06-12 10:10 GMT+02:00 Tony Marston :
> And what is the benefit in userland?
That is the question.
I think clean global namespace isn't enough argument, we can exist in
the current situation and considering the fact that most of the new
PHP applications have their own namespaces, it could pro
/cc-ing internals, as I sent the message privately to Yasuo by mistake.
-- Forwarded message --
From: Jakub Kubíček
Date: 2015-06-11 0:40 GMT+02:00
Subject: Re: [PHP-DEV] Migrating PHP classes to built in namespace
To: Yasuo Ohgaki
Hi.
This is weird and ugly what you
>
> Hi,
>
Hi Benjamin.
I have a question: is there any reason to throw an exception from
__toString, *other* than a non-recoverable error, which would denote that
the object, which the __toString method is called on, does not have any
meaningful string representation? Because if not, core impleme
Hi Internals,
I have recently made a patch[1] for PHP7 that replaces dead and obsolete
HTML code (like , vs. <...
id="..."> or XHTML's NET notation vs. HTML's ), mostly
being output by PHP itself (error messages, phpinfo() etc.), with
alternatives that are being used rather nowadays.
I would ap
+1 for this.
Best regards,
Kubo2
2015-04-24 15:10 GMT+02:00 Benjamin Eberlei :
> On Fri, Apr 24, 2015 at 12:24 PM, Olivier Garcia
> wrote:
>
> > Greetings Internals,
> >
> > A few weeks ago, Patrick (patrickalla...@php.net) and I wrote a RFC
> > [1] to improve the error callback mechanism and
Hey Alexander!
2015-04-22 10:26 GMT+02:00 Alexander Moskalev :
> Jakub, I think about static factory methods, but not sure if it will be
> great.
> I think using empty constructor more clear.
>
So we can add a setter, which, however, will return $this, to allow
chaining and prevent one redundan
My opinion is, that we simply have to change PHP closures' scoping to be
more similar with JavaScript functions' scope. That would solve the current
challenge pointed on by @jpauli, thus closure would have access to private
object's members only if it was defined in that object's class / method
def
So, get directly to your questions:
>
> 1) Can we still integrate this functionality to existing class CURLFile?
I think it would be possible, because like @smalyshev said, CURLFile
represents symbolic file, that is going to be uploaded with CURL. So my
suggestion would be creating a static fact
I would rather appreciate run-time class properties initialization.
Best regards,
Kubo2
2015-04-13 15:37 GMT+02:00 Johannes Ott :
> Hi,
>
> finally I managed to do my first RFC draft.
>
> https://wiki.php.net/rfc/static_class_constructor
>
> I hope I have done everything correct so far an
20 matches
Mail list logo