Hello!
>
It should behave exactly the same as the existing closing tag,
except that it does not erase the trailing newline character.
Thanks!
--
Shinji Igarashi
2022年6月6日(月) 6:54 Mark Baker :
>
> On 05/06/2022 10:23, shinji igarashi wrote:
> > I'd like to propose adding a new closing tag `=?>`
> or ."\n"
Yeah, adding an explicit newline character is a workaround for this.
However, what if that output content were moved to a location other
than the end of a line when editing the template? It would be
necessary to remove the extra newline character each time
they move from the end of a
Hello Internals,
I opened the vote about Stricter implicit boolean coercions as
announced. The vote will run until 2022-06-20.
Discussion: https://externals.io/message/117732
RFC: https://wiki.php.net/rfc/stricter_implicit_boolean_coercions
Best regards,
Andreas Leathley
On 05/06/2022 10:23, shinji igarashi wrote:
I'd like to propose adding a new closing tag `=?>` to the language.
PHP currently removes the newline character immediately following
the closing tag `?>`.
So we would have 4 possible combinations that developers could apply in
their code, two exist
On Sun, Jun 5, 2022 at 9:24 AM shinji igarashi wrote:
> Hello everyone,
>
> I'd like to propose adding a new closing tag `=?>` to the language.
>
> PHP currently removes the newline character immediately following
> the closing tag `?>`.
>
Personal opinion, seems like a classic sledgehammer on a
Hello everyone,
I'd like to propose adding a new closing tag `=?>` to the language.
PHP currently removes the newline character immediately following
the closing tag `?>`.
With the new closing tag `=?>`, the code should look like this:
```
-
-
-
```
and the results it produces would be:
`
