On Thu, Aug 6, 2020 at 12:30 PM Benas IML wrote:
> Hey Theodore,
>
> On Thu, Aug 6, 2020, 8:05 PM Theodore Brown wrote:
>
> > While none of our syntax options are perfect, I believe @@ has the
> > best long-term tradeoffs because:
> >
> > - It doesn't break useful syntax
>
> Fair enough.
>
>
Hey Theodore,
On Thu, Aug 6, 2020, 8:05 PM Theodore Brown wrote:
> On Thu, Aug 6, 2020 at 5:24 AM Benas IML
> wrote:
>
> > On Thu, 6 Aug 2020 at 11:45, Rowan Tommins
> wrote:
> >
> > > On Thu, 6 Aug 2020 at 09:12, Benas IML
> wrote:
> > >
> > > > But by sacrificing a few very old codebases
On Thu, Aug 6, 2020 at 5:24 AM Benas IML wrote:
> On Thu, 6 Aug 2020 at 11:45, Rowan Tommins wrote:
>
> > On Thu, 6 Aug 2020 at 09:12, Benas IML wrote:
> >
> > > But by sacrificing a few very old codebases (that still use `#` not `//`)
> >
> > Do you have some basis for # only being used by
> Le 6 août 2020 à 10:11, Benas IML a écrit :
>
> Ending delimiter MAY help us in the future.
>
> I really, really hate all of those arguments stating "that we should care
> only about the present, not the future" and that even though
> `#[...]`/`@[...]` might bring benefits in the future, we
A grep search was done by someone in the mailing list in the original
`<<...>>` to `@@...` RFC thread when discussing whether `#[` is going
to be a huge BC or not.
Just about all of the matches were either from old codebases or from
old PHP 3-5 Metasploit exploits, which are about 5-15 years old.
PHP 8.0.0beta1 has just been released and can be
downloaded from https://downloads.php.net/~carusogabriel
Or use the git tag: `php-8.0.0beta1`
Windows binaries are available at https://windows.php.net/qa
Please test it carefully, and report any bugs in
the bug system: https://bugs.php.net
The PHP development team announces the immediate availability of PHP
7.3.21. This is a security release.
All PHP 7.3 users are encouraged to upgrade to this version.
For source downloads of PHP 7.3.21 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
On 06.08.2020 08:50, Dmitry Stogov wrote:
> My solution:
>
> - remove doc-comment trigger. It doesn't make sense.
> - add @@Jit("off") only. Later we may extend this.
There are pros and cons to the "Jit" attribute name, please consider
@@JitOff (and @@JitOn).
Also make sure to define what
On Thu, 6 Aug 2020 at 09:12, Benas IML wrote:
>
> But by sacrificing a few very old codebases (that still use `#` not `//`)
>
Do you have some basis for # only being used by "very old" codebases? As
far as I'm aware, it's not deprecated, and while the PEAR style guide
listed it as
On Thu, Aug 6, 2020 at 9:18 AM Côme Chilliet <
come.chill...@fusiondirectory.org> wrote:
> Le Thu, 6 Aug 2020 07:48:05 +0100 (BST),
> Derick Rethans a écrit :
> > From the RFC:
> > - No ending delimiter
>
> As said before, it does have an ending delimiter when they are arguments
> since
> there
On Thu, 6 Aug 2020 at 07:40, Derick Rethans wrote:
> On Wed, 5 Aug 2020, Rowan Tommins wrote:
> > The confusing thing about this argument is that as soon as they have
> > arguments, attributes will have an ending delimiter _whatever_ syntax
> > we choose, because nobody has ever proposed
Hi,
The PHP development team announces the immediate availability of PHP
7.2.33. This is a security.
All PHP 7.2 users are encouraged to upgrade to this version.
For source downloads of PHP 7.2.33 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
The
On Thu, Aug 6, 2020, 10:18 AM Côme Chilliet <
come.chill...@fusiondirectory.org> wrote:
> Le Thu, 6 Aug 2020 07:48:05 +0100 (BST),
> Derick Rethans a écrit :
> > From the RFC:
> > - No ending delimiter
>
> As said before, it does have an ending delimiter when they are arguments
> since
> there
On Thu, 6 Aug 2020 at 08:18, Côme Chilliet <
come.chill...@fusiondirectory.org> wrote:
> As said before, it does have an ending delimiter when they are arguments
> since
> there is the parenthesis around them. When there are no arguments I don’t
> see
> the benefit of an ending delimiter, it’s
Le Thu, 6 Aug 2020 07:48:05 +0100 (BST),
Derick Rethans a écrit :
> From the RFC:
> - No ending delimiter
As said before, it does have an ending delimiter when they are arguments since
there is the parenthesis around them. When there are no arguments I don’t see
the benefit of an ending
On Wed, 5 Aug 2020, Rowan Tommins wrote:
> On 05/08/2020 18:10, David Rodrigues wrote:
>
> > With error supression remotion (9.0?) it could be used for other new
> > features easily.
>
>
> Just to re-iterate something that I'm pretty sure has been said
> before: the chance of removing the
My solution:
- remove doc-comment trigger. It doesn't make sense.
- add @@Jit("off") only. Later we may extend this.
On Tue, Aug 4, 2020 at 11:11 AM Benjamin Eberlei
wrote:
> On Mon, Aug 3, 2020 at 7:44 PM Benjamin Eberlei
> wrote:
>
> > Hi,
> >
> > I am going to pick up a discussion from
>
On Tue, 4 Aug 2020, Theodore Brown wrote:
>
> #[Attr1, Attr2] # 15 chars
>
> @@Attr1 @@Attr2 # 15 chars
>
> # 4 lines, 53 chars not counting whitespace
> @[
> AttrWithParam("foobar"),
> SomeOtherAttr("fizzbuzz"),
> ]
>
> # 2 lines, 52 chars
>
On Wed, 5 Aug 2020, Rowan Tommins wrote:
> On Wed, 5 Aug 2020 at 13:20, Benjamin Eberlei wrote:
>
> > It looks nice for a simple attribute like @@Jit, or for a one
> > without arguments like the used @@Deprecated, but as soon as there
> > are more than one, and they each get arguments,
19 matches
Mail list logo
