Hi, thanks for supporting this!
> Maybe just 2 days (of internals and Reddit feedback) is a bit early to
> "give up"
I kinda thought so too after I declared defeat, but...
The Feature Freeze for 8.2 is July 19!
The RFC process requires two weeks each for discussion and voting.
If we want to add
On 8 June 2022 20:22:46 BST, Aaron Junker wrote:
>Hi all,
>
>I've edited my RFC[1], so it now contains a note that edit.php.net is
>currently not in a usable state.
>
>Besides that, I didn't find any big points that could have been added to the
>RFC.
>
>So, unless a big new discussion starts, I
On 08/06/2022 20:22, Aaron Junker wrote:
But I have two questions:
1. What kind of majority in votes will this RFC need to get accepted?
2. Am I allowed to vote on my own RFC?
While this is a somewhat unusual RFC, because it's a change to the
project / infrastructure, not the language itself
Hi all,
I've edited my RFC[1], so it now contains a note that edit.php.net is currently
not in a usable state.
Besides that, I didn't find any big points that could have been added to the
RFC.
So, unless a big new discussion starts, I will open votes this Saturday.
But I have two questions:
On Wed, 8 Jun 2022 at 20:16, shinji igarashi wrote:
> > declare(ignore_newline_after_close_tag=false);
>
> Thanks for coming up with another idea!
>
> As others have already pointed out, disabling the closing tag from
> eating trailing newline throughout the file would be inconvenient if
> we wan
> declare(ignore_newline_after_close_tag=false);
Thanks for coming up with another idea!
As others have already pointed out, disabling the closing tag from
eating trailing newline throughout the file would be inconvenient if
we want to use control statements in the template.
However, we currentl
Hello!
> I think you may just be dealing with a vocal minority and it would be worth
> putting to
> an actual vote. Even if it fails, we'll learn something the next time
> someone wants to change something like this.
Thanks for the feedback!
In my experience over the years of watching internals
> Declare statements shouldn't have any impact outside of the file in which
> they appear. Declaring strict types doesn't force other classes that
> interact with the defined class to also use strict types. A declare to
> change how newlines after closing tags are handled within a single file
> for
On Wed, Jun 8, 2022 at 5:37 AM Claude Pache wrote:
>
>
> > Le 8 juin 2022 à 05:34, Sara Golemon a écrit :
> >
> >
> > > declare(ignore_newline_after_close_tag=false); // defaults to true, i.e
> > existing behavior
> >
> > This would avoid any new syntax rules, but still provide the ability for
Hi,
> https://github.com/php/php-src/pull/8708
> https://www.reddit.com/r/PHP/comments/v5le6h/adding_new_closing_tag_for_keeping_trailing/
Thanks for proposing! this "feature" bothered me more than once...
Maybe just 2 days (of internals and Reddit feedback) is a bit early to
"give up" (but I wo
> Le 8 juin 2022 à 05:34, Sara Golemon a écrit :
>
>
> declare(ignore_newline_after_close_tag=false); // defaults to true, i.e
> existing behavior
>
> This would avoid any new syntax rules, but still provide the ability for
> php-as-template-engine to behave in the user's preferred mode.
>
On Wed, 8 Jun 2022, 08:15 CHU Zhaowei, wrote:
> > > declare(ignore_newline_after_close_tag=false); // defaults to true, i.e
> > existing behavior
>
> > This would avoid any new syntax rules, but still provide the ability for
> > php-as-template-engine to behave in the user's preferred mode.
>
>
12 matches
Mail list logo
