On 26 February 2024 23:11:16 GMT, Frederik Bosch wrote:
>And what happens in the following situation, how are multiple get calls
>working together?
>
>public string $fullName {
> get => $this->first . ' ' . $this->last; // is this accessing the backed
>value, or is it accessing via get
>
On 27-02-2024 10:49, Rowan Tommins [IMSoP] wrote:
On 26 February 2024 23:11:16 GMT, Frederik Bosch
wrote:
>And what happens in the following situation, how are multiple get
calls working together?
>
>public string $fullName {
> get => $this->first . ' ' . $this->last; // is this
>
> I hear you, but what about exit; ?!
> Do not worry exit; is still supported!
> It only requires a _tiny_ bit of dark magic to achieve this!
> exit; would just be interpreted as a fetch to a constant,
> so when attempting to access the undefined exit/die case-insensitive constant
> we just
2024年2月27日(火) 6:13 Tim Düsterhus :
>
> Hi
>
> On 2/26/24 10:56, Daniil Gentili wrote:
> > even ignoring all the deliverability issues, I don't think using a
> > mailing list is a good idea for a modern programming language, seeking
>
> And neither is GitHub Discussions. When I have the choice
> It sounds like most people are just really, really pissed off by an
implicit variable
I think that it could be good to follow the PHP way to mark the "magic"
stuff, which is putting leading underscores on the magic stuff. It's not
pretty, but it's good because our eyes can detect the magic stuff
Hey,
On Wed, Feb 21, 2024 at 7:58 PM Larry Garfield
wrote:
> Hello again, fine Internalians.
>
> After much on-again/off-again work, Ilija and I are back with a more
> polished property access hooks/interface properties RFC. It’s 99%
> unchanged from last summer; the PR is now essentially
Made a RFC draft: https://wiki.php.net/rfc/sleep_function_float_support
First time, so I'm not surprised if there are some mistakes there.
Feedback is very welcome.
I have tried sending this email 4 times over 2 days from hans at loltek dot
net and every time the email server said delivery
On Tue, Feb 27, 2024, at 17:16, Larry Garfield wrote:
> On Tue, Feb 27, 2024, at 10:01 AM, Frederik Bosch wrote:
>
> > Hi Rowan,
> >
> > Our discussion sums up the pros and cons. Whether yield is
> > complicated/confusing or not, is maybe personal. The same applies to
> > getting $this->prop
> VCS was already moved to github after the recent hack of the php VCS, a lot
> of technical internals-related discussion is already using exclusively github
> issues and pull request discussions, I believe that the mailing list is
> nothing more than a redundant relic of the past.
>
As one of
This is a test e-mail from a subscribed GMail address, to see if the
"451: Temporary lookup failure" errors are now resolved.
Thanks to those working on it!
--
Rowan Tommins
[IMSoP]
Hi internals
The RFC was accepted with 14 yes and 0 no votes.
Thanks to everyone who participated!
Kind regards
Niels
On 13/02/2024 20:49, Niels Dossche wrote:
> Hi internals
>
> I'm starting the vote on my RFC "Opt-in DOM spec-compliance".
> Voting will run until the 27th of February 21:00
-- Forwarded message -
From: Robert Landers
Date: Sat, Feb 24, 2024 at 9:20 AM
Subject: History of traits + inheritance
To: internals
I'm asking for a history lesson if anyone knows, as I couldn't find
any relevant information in externals and it appears to have been this
way
On 27/02/2024 17:49, Erick de Azevedo Lima wrote:
> It sounds like most people are just really, really pissed off by an
implicit variable
I think that it could be good to follow the PHP way to mark the
"magic" stuff, which is putting leading underscores on the magic stuff.
I think that
On Wed, Feb 21, 2024, 20:58 Larry Garfield wrote:
> Hello again, fine Internalians.
>
> After much on-again/off-again work, Ilija and I are back with a more
> polished property access hooks/interface properties RFC.
>
I liked how the discussion and the RFC evolved so far and that we have less
Hi
On 2/27/24 18:49, Rowan Tommins wrote:
This is a test e-mail from a subscribed GMail address, to see if the
"451: Temporary lookup failure" errors are now resolved.
Email successfully received, let's see whether my response is delivered
back to you via the list.
Best regards
Tim
On Tue, Feb 27, 2024, at 8:51 PM, Benjamin Außenhofer wrote:
> thank you for this proposal. there are some points i'd like to make
> into this discussion:
>
> * Thank you for the removal of $field, it was non-idomatic from a PHP POV.
>
> * I would prefer that the short syntax $foo => null; be
Hi Larry and others
On Fri, Feb 23, 2024 at 12:57 AM Larry Garfield wrote:
>
>
> I've added an FAQ section explaining why the Python/JS approach wouldn't
> really work. To be clear, Ilija and I spent 100+ hours doing research and
> design before we started implementation (back in mid-late
On Sun, Feb 25, 2024, at 10:16 PM, Rowan Tommins [IMSoP] wrote:
> [Including my full previous reply, since the list and gmail currently
> aren't being friends. Apologies that this leads to rather a lot of
> reading in one go...]
Eh, I'd prefer a few big emails that come in slowly to lots of
On Tue, Feb 27, 2024, at 10:01 AM, Frederik Bosch wrote:
> Hi Rowan,
>
> Our discussion sums up the pros and cons. Whether yield is
> complicated/confusing or not, is maybe personal. The same applies to
> getting $this->prop resulting in different calls. Larry has removed
> $field from the RFC
19 matches
Mail list logo
