Den 2015-08-19 kl. 15:55, skrev Ryan Pallas:
On Aug 19, 2015 6:44 AM, Björn Larsson bjorn.x.lars...@telia.com
mailto:bjorn.x.lars...@telia.com wrote:
Plan to migrate to PHP 7 later, like the new Exception/Error way
of working very much. Point is that current set_exception_handler
only
in PHP7*:
Errors signify programmer error, where Exceptions signify
unknown or runtime errors. Meaning that an Error should always be a
problem with your code, but an Exception could be a systems problem, a
user problem or a problem in your code.
/Cheers //Björn Larsson/
PS
Den 2015-08-19 kl. 15:18, skrev Anatol Belski:
-Original Message-
From: Pierre Joye [mailto:pierre@gmail.com]
Sent: Wednesday, August 19, 2015 10:19 AM
To: Sebastian Bergmann sebast...@php.net
Cc: PHP internals internals@lists.php.net
Subject: Re: [PHP-DEV] Re: [PHP-CVS] com
throwing
exceptions in PHP7*:
Errors signify programmer error, where Exceptions signify
unknown or runtime errors. Meaning that an Error should always be a
problem with your code, but an Exception could be a systems problem, a
user problem or a problem in your code.
/Cheers //Björn Larsson/
PS A bit
Den 2015-08-19 kl. 16:09, skrev Niklas Keller:
It surely won't be the last one. I am not keen to keep adding or
changing things
like that at this stage, given the tough timeline.
Yeah, there are quite some topics yet which unfortunately cannot be
resolved properly in the given time frame till
Den 2015-08-19 kl. 19:15, skrev Anatol Belski:
Hi,
-Original Message-
From: Sebastian Bergmann [mailto:sebast...@php.net]
Sent: Wednesday, August 19, 2015 4:21 PM
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Re: [PHP-CVS] com php-src: bump versions: configure.in
Den 2015-10-16 kl. 15:09, skrev Sammy Kaye Powers:
On Thu, Oct 15, 2015 at 8:28 PM, Marcio Almada
wrote:
Hi,
2015-10-14 16:25 GMT-03:00 Sammy Kaye Powers :
Hello internals friends!
I'd like to open a discussion on the RFC to allow trailing commas in
Den 2015-10-14 kl. 21:25, skrev Sammy Kaye Powers:
Hello internals friends!
I'd like to open a discussion on the RFC to allow trailing commas in
function arguments.
https://wiki.php.net/rfc/revisit-trailing-comma-function-args
Discuss! :)
Thanks,
Sammy Kaye Powers
sammyk.me
Given the
Den 2015-10-14 kl. 23:52, skrev Andrea Faulds:
Good evening,
I'm reviving my Void Return Type RFC, this time for PHP 7.1:
https://wiki.php.net/rfc/void_return_type
Please read it and tell me your thoughts!
Thanks.
P.S. As it so (fatefully?) happens, I originally introduced this on
14th
Den 2015-10-03 kl. 01:17, skrev Levi Morrison:
I messaged the list about this feature before I had the RFC written up
for it. The RFC[1] is slightly different from what I proposed in the
previous thread, so please read the RFC to make sure you understand
what is being proposed before replying
/void_return_type#why_call_it_void_and_not_null
Thanks.
Good summary and motivation! Should be a very good reason
to have any other name then void as return type.
r//Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2015-10-15 kl. 09:04, skrev Björn Larsson:
Den 2015-10-14 kl. 23:52, skrev Andrea Faulds:
Good evening,
I'm reviving my Void Return Type RFC, this time for PHP 7.1:
https://wiki.php.net/rfc/void_return_type
Please read it and tell me your thoughts!
Thanks.
P.S. As it so (fatefully
Den 2015-10-15 kl. 19:14, skrev Sara Golemon:
On Wed, Oct 14, 2015 at 11:59 PM, Björn Larsson
<bjorn.x.lars...@telia.com> wrote:
Given the reason against this RFC in the thread it would be interesting
to know why HHVM decided to implement it?
Happy to answer, but I need to state a
set_exception_handler catching same type of
exceptions like
in PHP 5?
Regards //Björn Larsson
//
Den 2015-08-26 kl. 13:19, skrev Niklas Keller:
Hi Björn,
Ah yes, then a set_throwable_handler would be needed. A final question:
Would it
be an alternative to update set_error_handler to also handle
\Throwable\Error\*
exceptions and let set_exception_handler catching same type of exceptions
-baked
but it was a separate RFC for 7.0.
Regards //Björn Larsson
|
|
the proposal,
take it or leave it".
Really appreciate that! Like the idea but the variation in syntax forms
is a bit confusing. Maybe one start with a very simple function and as
as you expand it the syntax form needs to change which I think is a
drawback.
Regards , //Björn Larsson
--
PHP
$accumulator=$initial;
foreach($inputas$value){
$accumulator=$fn($accumulator,$value);
}
return$accumulator;};
}
Or maybe I'm just overly familiar having function arguments
within parenthesis ;)
Regards, //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2015-09-10 kl. 22:22, skrev Bob Weinand:
Am 10.09.2015 um 22:04 schrieb Björn Larsson <bjorn.x.lars...@telia.com>:
Den 2015-09-03 kl. 00:48, skrev Rowan Collins:
Amendment 3. Make the parentheses around the argument list mandatory so that (if Amendment 1
is also adopted) there i
Den 2015-09-28 kl. 18:53, skrev Levi Morrison:
On Mon, Sep 28, 2015 at 9:17 AM, Thomas Hruska wrote:
On 9/28/2015 1:29 AM, S.A.N wrote:
Are there any future plans for - async/await?
This need to know now, not to use these words to constants, and class
names...
or if someday in the future comparison operator
without type juggling is needed.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
sion] Short Closures
Date: Sun, 6 Sep 2015 17:59:57 -0700
From: Sara Golemon <p...@golemon.com>
To: Bob Weinand <bobw...@hotmail.com>
Copy: Björn Larsson <bjorn.x.lars...@telia.com>, PHP Internals
<internals@lists.php.net>
Regards //Björn Larsson
(Resending, because I accid
Den 2015-10-01 kl. 19:12, skrev Bishop Bettini:
On Thu, Oct 1, 2015 at 12:28 PM, Anthony Ferrara
wrote:
Nikita and all,
I don't think there was a dozen of different ideas, I could only find
those
about `lambda(arg-list; use-list; expression)` and variations of it with
Hi,
Given the recent discussion about async/await keyword should one
also consider short closures supporting asynchronous functionality
in the future?
Stumbled upon it when reading about Async Lambdas in Hacklang
manual.
Regards //Björn Larsson
Den 2015-09-26 kl. 18:17, skrev Levi Morrison
t; $x * 2] seems ambigous, from reader's POV; key of
the item is result of fn($x) and value is $x * 2? Also, it would be a
huge BC break with not allowing you to name functions fn(), wouldn't
it?
--
Regards
Pavel Kouřil
Being a userland developer myself I totally agree! Keeping it simple,
consistent & unambiguous.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2015-10-02 kl. 18:50, skrev Sara Golemon:
On Mon, Sep 28, 2015 at 2:29 PM, Björn Larsson
<bjorn.x.lars...@telia.com> wrote:
... or if someday in the future comparison operator
without type juggling is needed.
You just blew my mind. Trying to imagine where strict
greater-than-or
if syntax was
made a choice between ~> and ==> as a voting option.
How does one then address that this RFC only covers a subset of
Hacklang functionality when having the same operator?
--
//Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
Den 2015-09-22 kl. 03:59, skrev Bob Weinand:
Hey,
Thanks for all your feedback in the discussion thread!
So, before I start the vote, just two quick notes:
I've added two notes about the statement syntax and the single variable use.
Though a few people complained, I'm not switching to the ==>
functionality of any other language.
In principal I agree, but by using the same operator one sets an
end-user expectation that the functionality is close to the same.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2015-09-22 kl. 17:16, skrev Andrea Faulds:
Hi Bob,
Bob Weinand wrote:
Hey,
Thanks for all your feedback in the discussion thread!
So, before I start the vote, just two quick notes:
I've added two notes about the statement syntax and the single
variable use.
Though a few people
thanks for a
very professional job getting #PHP7 out of the door!
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2015-12-03 kl. 13:44, skrev Martin Keckeis:
2015-12-02 21:02 GMT+01:00 Andrea Faulds :
Hi Martin,
Martin Keckeis wrote:
i think it's time to deprecate the function get_browser().
The reason is simple: Since the browscap.ini file has grown a lot this
function does need way
Den 2015-12-06 kl. 17:39, skrev François Laupretre:
Le 06/12/2015 13:38, Zeev Suraski a écrit :
-Original Message-
From: Jan Ehrhardt [mailto:php...@ehrhardt.nl]
Sent: Sunday, December 06, 2015 2:15 PM
To: internals@lists.php.net
Subject: [PHP-DEV] PHP 5.6 life cycle
See
Den 2015-12-08 kl. 16:00, skrev Adam Howard:
The EOL (end of life) date does influence people. True, not everyone will
simply jump ship upon EOL. But it is still has a significant enough
influence on adoption and urgency in general. Especially toward new
development projects or new releases
Den 2015-12-06 kl. 18:05, skrev Sebastian Bergmann:
Am 06.12.2015 um 17:57 schrieb Björn Larsson:
Would like to add that given 7.0 major uptake with ISP's coming next
year (at least in my region) it seems prudent to prolong 5.6 lifecycle a
little.
I fear that extending support for PHP 5
Den 2015-12-07 kl. 16:57, skrev Zeev Suraski:
-Original Message-
From: Arvids Godjuks [mailto:arvids.godj...@gmail.com]
Sent: Monday, December 07, 2015 5:52 PM
To: Zeev Suraski
Cc: Rowan Collins; PHP internals
Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle
According to PHP release RFC -
Den 2015-12-09 kl. 20:46, skrev Mike Willbanks:
Lester,
On Wed, Dec 9, 2015 at 1:02 PM, Lester Caine wrote:
On 09/12/15 16:24, Rowan Collins wrote:
So as somebody already said, maybe your code or setup is really busted.
Really busted, or spending all its time in a type
Den 2015-12-10 kl. 12:16, skrev Lester Caine:
On 10/12/15 11:02, Björn Larsson wrote:
Just noticed that Smarty team is working on a 3.1.28 relase that plans
to be PHP 7 compliant, see: https://github.com/smarty-php/smarty
The version I'm running is not giving any errors, similarly ADOdb. Both
Den 2015-11-23 kl. 08:28, skrev Anatol Belski:
Hi,
-Original Message-
From: Rasmus Lerdorf [mailto:ras...@lerdorf.com]
Sent: Sunday, November 22, 2015 11:20 PM
To: Anthony Ferrara ; Zeev Suraski
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV]
d for making
libsodium fly and what is unrealistic (needs to be handled outside
libsodium)
even if we talk about 7.x perspective?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
rce_type()
[1] http://programmers.stackexchange.com/questions/162698
One could add that not all development / debugging is done through
an advanced IDE. Logging in to production server with SSH ending up
with a terminal window, only having Emacs or Vi at your disposal is
still valid today.
Regards //Bj
beit small.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2016-06-17 kl. 11:19, skrev Rowan Collins:
On 17/06/2016 10:08, Björn Larsson wrote:
And pardon me, but saying that we can wait until an PHP 8.0 release
that we have no clue about when it will happen sounds in my eyes
a bit to far off. Going that direction means instead that boiler plate
s
a bit to far off. Going that direction means instead that boiler plate
code is needed to catch that exact number of parameters is sent.
So I wonder are we here making a hen out of a feather? But of course
if the release process needs clarifying then do it, but please keep the
feature as is.
Den 2016-06-17 kl. 12:15, skrev Rowan Collins:
On 17/06/2016 10:49, Björn Larsson wrote:
Well one reason I could think of is that things that get postphoned,
is not the same thing as meaning it will get done in the future.
Again, I am not proposing we indefinitely postpone anything. I am
to extend this though if people don't think they'll
have time to review it within the next week.
Regards //Björn Larsson
-Tom
Well, even if it's small one there could be a value in having a slightly
longer voting period. Just thought that many CoC mails
Den 2016-01-18 kl. 13:22, skrev Lester Caine:
On 18/01/16 08:12, Yasuo Ohgaki wrote:
Large numeric literals are not used often. However if it is used, it's
frustrating to read. e.g. Code audit/review. Why not make computer
do the job?
I hope more people change their mind.
Where large numbers
Den 2016-01-16 kl. 02:40, skrev Andrea Faulds:
Hi Thomas,
Thomas Punt wrote:
Hi internals!
Voting has opened for the inclusion of a digit separator in PHP[1].
Voting ends in
one week's time on January 20th.
Thanks,
Tom
[1]: http://wiki.php.net/rfc/number_format_separator
Initially I
a vote it would definetly be +1. A small question
though, why is the voting period only one week (small RFC or)?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ementation of generics?
Regards //Björn Larsson
PS Then we of course have the famous
https://github.com/ircmaxell/PhpGenerics
to lean on ;-)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
porarily deprecated.
>
> I think deprecating it was a mistake and give how much semantic load []
> carries - array access, array constructor, now there's proposal to make
> it used in deconstructing too - adding string offset to it looks like
> bad idea. Different things should use dif
ine I find this approach quite promising. Good luck
with it!
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ad to a not pass.
Judging from the discussion it didn't seem like there
was resources to make a bigger thing, meaning that
this small addition would not be part of PHP in the
the short to medium-term perspective.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscr
participated in the RFC discussion and voting!
-Tom
Thanks for the good work. Many voters but not so
much discussion on the list before voting. Slightly
surprised it didn't pass actually.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
le code like this one that I
found in symfony (not really a big deal but still)
} catch (AccessException $e) {
return false;
} catch (UnexpectedTypeException $e) {
return false;
}
And other piece of code using multiple libraries.
On 8 March 2016 at 18:06, Björn Larsson <bjorn.x.lars...@t
Den 2016-03-16 kl. 17:36, skrev Phil Sturgeon:
Hello everyone,
I have completed the draft for an RFC, to add Typed Properties. The
patch has been written by the one and only Joe Watkins.
https://wiki.php.net/rfc/typed-properties
I would really appreciate constructive feedback on this RFC,
Den 2016-03-14 kl. 19:14, skrev Colin O'Dell:
Forcing people to specify a visibility for properties and not for methods
would add yet another inconsistency in the language.
That's a really good point. However, I think we currently have a different
inconsistency: declaring functions without
target for this is custom exceptions or
the built-in ones or both?
Regards //Björn Larsson
PS
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2016-03-18 kl. 21:12, skrev Fleshgrinder:
On 3/17/2016 9:03 AM, Benjamin Eberlei wrote:
Sorry to dampen your enthusiasm, but you are going slightly off topic here.
Package visibility was tried by Guilherme Blanco before, the way namespaces
are implemented this is not possible in PHP in an
Den 2016-03-29 kl. 22:38, skrev Phil Sturgeon:
On Tue, Mar 29, 2016 at 2:58 PM, Björn Larsson
<bjorn.x.lars...@telia.com> wrote:
Den 2016-03-29 kl. 17:32, skrev Phil Sturgeon:
I'd like to thank everyone for their feedback on this RFC!
It looks like the majority of concerns were solved
is already started.
Midori
On 30 Mar 2016, at 22:22, Björn Larsson <bjorn.x.lars...@telia.com> wrote:
Hi,
Think the word equal should be removed from RFC name so
it becomes "Null Coalescing Assignment Operator" or?
Also on the page https://wiki.php.net/rfc, possible to c
the
engine to return null.
Don't have a strong opinion on this one, can see both views.
Maybe a bit affected by programming in Java recently, having
a slightly more positive attitude towards default values ;-)
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscr
Den 2016-04-07 kl. 21:11, skrev Markus Fischer:
Hey,
On 07.04.2016 14:21, Andrea Faulds wrote:
Bob and I have made an RFC which proposes an alternative syntax for list():
https://wiki.php.net/rfc/short_list_syntax
Please tell us your thoughts.
Reading the last sample in the RFC:
Both
Den 2016-03-19 kl. 13:29, skrev Fleshgrinder:
On 3/19/2016 1:19 PM, Björn Larsson wrote:
Hi,
There is "references" in the message header so it ends up in the
same thread in Thunderbird newsreader but with a new headline.
In case you want to repost...
I think it's a good starting po
e for null
coallesce.
-Sara
On Thu, Mar 24, 2016 at 8:46 AM, Midori Kocak <mtko...@gmail.com> wrote:
there were no suggestions. Do you have one?
On 24 Mar 2016, at 16:36, Björn Larsson <bjorn.x.lars...@telia.com> wrote:
Den 2016-03-13 kl. 02:59, skrev Andrea Faulds:
Hi Midori,
Den 2016-03-24 kl. 21:29, skrev Andrea Faulds:
Hi Patrick,
Patrick ALLAERT wrote:
Hi Andrea,
Nice work.
I'm globally +0.7 on it, there is however a few things that are
unclear to
me:
* What happens with an empty string? Warning, notice or even nothing?
* Would:
42 + "";
produce the same
-7
# In Appendix B
- http://www.php7book.com
# At the end of every chapter
Regards //Björn Larsson
PS Maybe best to finish implementation and tests first.
Den 2016-04-03 kl. 03:17, skrev Midori Kocak:
Dear All,
Based on the concerns I wrote some tests. Can you check those and give
feedback
Den 2016-03-29 kl. 17:32, skrev Phil Sturgeon:
I'd like to thank everyone for their feedback on this RFC!
It looks like the majority of concerns were solved during the course
of this discussion, which is great news.
The RFC has been expanded in a few areas to take care of a few other
concerns,
with some more examples, maybe not
feasible given that the voting is over.
- Update RFC with link to Ruby.
What do you think? Anyway, I'm not so privy to the RFC process
so maybe this is a non issue...
Regards //Björn Larsson
Den 2016-03-25 kl. 13:46, skrev Midori Kocak:
http://www.rubyinside.com
Hi,
Thanks for a well specified RFc and I got a nifty script to
update my old PHP 5.2 code :-)
Regards //Björn Larsson
Den 2016-03-31 kl. 14:41, skrev Colin O'Dell:
The voting period for the "var deprecation" RFC has ended. The final vote
was 31 in favor and 23 against. The 2/
Good evening,Den 2016-03-31 kl. 10:34, skrev Joe Watkins:
Morning,
Given that public is implied for all properties above there
is a value in having the same rule for type.
public $bar, int $foo;
What does this mean?
If it's not an error, what does this mean ?
public $bar, int $foo, $qux;
".
Regards,
Hm... In Hack the above code works, see:
https://3v4l.org/nsA5W
Well they have a different implementation as mentioned in
the RFC, so no wonder. But they do have typed porperties in
the language.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To u
tion($e); // Hide which libraries we're using to
implement the function
}
Regards,
Good example, thats how I would use multi-catch.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
and put
it into vote quickly, maybe having you both as authors or one of
you taking the lead? And again, sorry if I jump into the discussion
uninvited.
/Regards //Björn Larsson/
Den 2016-04-28 kl. 21:16, skrev Dmitry Stogov:
Levi, I provided an implementation for your RFC on February 2015, and I
Den 2016-04-19 kl. 01:24, skrev Sara Golemon:
On Tue, Apr 12, 2016 at 7:38 PM, Sara Golemon wrote:
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")
I haven't heard any responses on this and
f we decided to live with doc-comments only.
Thanks. Dmitry.
Thanks for the good work. Regarding naming, I googled
"PHP attributes" vs "PHP annotations" and looking at the
result, my view is that that Annotation is a better naming
then Attributes. Any hope in changing it?
Re
Den 2016-05-11 kl. 00:00, skrev Dmitry Stogov:
On 05/11/2016 12:29 AM, Björn Larsson wrote:
Den 2016-05-10 kl. 20:29, skrev Dmitry Stogov:
Hi internals,
I've started voting on "PHP Attributes" RFC.
https://wiki.php.net/rfc/attributes
In my opinion, "PHP Attributes&qu
Hi,
Nice and clear-cut RFC! One reflection is if the usage of use
to "import" variables could have an impact on a proposal
for a short form of Lambda functions in the future?
Cheers //Björn
PS I liked the Short Closure RFC btw.
Den 2016-04-26 kl. 10:25, skrev Joe Watkins:
Morning internals,
the earlier example "binary tree" in Introduction? I
think it served as one good UC why this feature is needed. I also think
one could expand the reference section with some of the ones from:
- https://wiki.php.net/rfc/nullable_return_types#references
Regards //Björn Larsson
--
PHP Inter
Den 2016-04-14 kl. 16:25, skrev Levi Morrison:
On Thu, Apr 14, 2016 at 3:12 AM, Derick Rethans wrote:
On Wed, 13 Apr 2016, Levi Morrison wrote:
As alluded to in an earlier email today[1] I am now moving the Union
Types RFC[2] to the discussion phase. The short summary of the
Den 2016-04-15 kl. 19:58, skrev Dmitry Stogov:
A week ago, I actually wrote my own RFC
https://wiki.php.net/rfc/nullable_return_types
but didn't push it for discussion in favor of Levi's nullable_type RFC (they
are almost the same).
I'm sure, union types bring too many conceptual and
is feature reminds me about Group Use declarations,
adding syntax sugar to improve code quality and make
code updates less error prone.
Regards //Björn Larsson
PS Typo in "usefull", think it's only one l.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
Hi,
Den 2016-04-06 kl. 18:33, skrev Phil Sturgeon:
On Sat, Apr 2, 2016 at 3:10 PM, Björn Larsson <bjorn.x.lars...@telia.com> wrote:
Good evening,Den 2016-03-31 kl. 10:34, skrev Joe Watkins:
Morning,
Given that public is implied for all properties above there
is a value in having th
at the operator was a bit controversial due to
e.g. japanese keyboard. Personally I liked the proposal
and I think the "pipe" sign fit well into an pipe operator:)
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ith the proposed
semantics.
Nikita
Maybe one should split the vote into separate for each function.
I mean pity if vote fails because one function is not attractive while
the other one is...
What do you think?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing Lis
in the future
would have async / await functionality. How does that
play together with arrow functions? HHVM has some
example: https://docs.hhvm.com/hack/async/blocks
Anyway, I do appreciate that finally arrow functions in
PHP are on the horizon :-)
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
github.com/php/php-src/pull/1902
Regards,
Yup, personally I do find this a worthwhile effort! Would fixing
this behaviour also be applicable for HTTPS?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
There was / is a proposal about bigints, see:
https://wiki.php.net/rfc/bigint
Regards //Björn Larsson
Den 2016-08-29 kl. 15:48, skrev David Rodrigues:
Currently PHP integer is limited to 2147483647 or 9223372036854775807
(PHP_INT_MAX), depending of system bits. We can works with long
I think you will find information about this in the threads
for discussion and voting regarding Nullable types RFC:
- https://marc.info/?l=php-internals=14606054028
- https://marc.info/?l=php-internals=146289381815830
- https://wiki.php.net/rfc/nullable_types
Regards //Björn Larsson
Den
them!
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
This RFC was done close to 4 years ago when PHP 7 was not on
the table. So, I wonder if the performance implications are the
same, now that there is a new flashy PHP 7 engine?
Regards //Björn Larsson
Den 2016-12-19 kl. 23:47, skrev Larry Garfield:
On 12/19/2016 02:57 PM, ilija.tov
version of the syntax or
only one?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ture itself. Any plans to go with this for 7.2?
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den 2017-08-12 kl. 02:37, skrev Andreas Hennings:
This is true, I remember having done it in the past.
I still think it would be nice and feel natural to have the default
values directly built into the list construct.
It would be a bit faster, because it does not have to allocate a new
Den 2017-05-31 kl. 00:26, skrev Levi Morrison:
On Tue, May 30, 2017 at 3:37 PM, Björn Larsson
<bjorn.x.lars...@telia.com> wrote:
Den 2017-05-30 kl. 21:40, skrev Derick Rethans:
On Tue, 30 May 2017, Levi Morrison wrote:
Internals,
The previous discussion thread has died down signifi
Den 2017-05-30 kl. 21:40, skrev Derick Rethans:
On Tue, 30 May 2017, Levi Morrison wrote:
Internals,
The previous discussion thread has died down significantly and so I'd
like to start a new one to refocus. This message has some redundant
information by design so people don't have to
Den 2017-05-30 kl. 04:48, skrev Levi Morrison:
On Mon, May 29, 2017 at 4:47 AM, Björn Larsson
<bjorn.x.lars...@telia.com> wrote:
Den 2017-04-05 kl. 23:57, skrev Levi Morrison:
Any plans to go with this for 7.2?
I have been working on this RFC a bit in the last two weeks and intend
to
Den 2017-06-01 kl. 18:58, skrev Theodore Brown:
On Tuesday, May 30, 2017 at 12:58 PM, Levi Morrison wrote:
Based on the discussion there are a few different syntax choices
people liked. Overall it's a feature that people seem to want but
everyone seems to prefer a different syntax choice.
1.
Den 2017-06-07 kl. 17:20, skrev Stephen Reay:
On 7 Jun 2017, at 20:37, Björn Larsson <bjorn.x.lars...@telia.com> wrote:
Well, one reason to use fn or even lambda was to signal that this is
different then a regular function.
When it comes to number of keystrokes I guess that some inspi
Den 2017-06-08 kl. 15:34, skrev Rowan Collins:
On 08/06/2017 13:33, Björn Larsson wrote:
One reason
(not the only one) for me to advocate ==> syntax is that it's the
same syntax as HACK
I'm not a fan of this logic. Using Hack as a kind of
prototyping-ground for PHP features is f
1 - 100 of 249 matches
Mail list logo