>> As we are creating new syntax, why not simply use another single
>> symbol? Here are some examples:
>>
>> ```php
>> *Deprecated
>> %Deprecated
>> >Deprecated
>> &Deprecated
>> function foo() { }
>> ```
>>
>> I'm not 100% sure if all this symbols could by used in that context,
>> but I think I prefer any of them rather than a double symbol.
>>
>> Would it be possible to add a multioption vote and let people choose?
>
> Hi Iván,
>
> No, I don't believe possible to use any of those symbols. * already
> means multiplication, % is used for modulus, > is for boolean
> comparison, and & is for references.
>
> The point of the RFC isn't to change styles to match a personal
> preference about looks, but to solve several concrete shortcomings
> with `<<>>` as laid out in the RFC.

Hi Theodore,

Yes, in other context they are operators; the same that << and >>, the bitwise 
shift operators, and the current syntax is already using them with a different 
meaning.

The ones I put in my original message were just examples of tokens we could 
use, maybe “&” can’t be used because it can conflict with references, but there 
are some others I think can be used. Let’s bringing them all together:

// From my original message:
*Deprecated
%Deprecated
>Deprecated
function foo() { }

// New ones:
:Deprecated
=Deprecated
function foo() { }

We are looking at what other languages are doing, but currently PHP “supports” 
(not natively) *attributes in docblock comments, and it’s a fairly used feature:

/**
* @Deprecated
*/
function foo() {}

The closest usable token with one and two symbols would be * and *@ 
respectively. Anyhow @@ seems faster to type than *@.


Anyway, what I was trying to expose is that, as we can not directly adopt 
syntax for another language, maybe it would be better to not introduce a 2 
chars token with BC breaks, and maybe go with a even shorter token with no BC 
breaks.

Which token? I think there are a lot of them we can use, and for sure anyone 
has its preference; and that’s why I was also suggesting to pick a few of them, 
vote them in the RFC, and go with the winner.

Regards,
Iván Arias.

Reply via email to