Re: [RFC] Explicit call-site send-by-ref syntax
| From: | lists@rhsoft.net | Date: | Sat, 09 Dec 2017 02:15:12 +0000 |
| Subject: | Re: [RFC] Explicit call-site send-by-ref syntax | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-101272@lists.php.net to get a copy of this message | ||
Am 08.12.2017 um 18:55 schrieb Stephen Reay:
i responded to Björn's response and when someone than quotes me and refer to a side thread i am really not guiltyOn 8 Dec 2017, at 5:16 pm, lists@rhsoft.net <mailto:lists@rhsoft.net> wrote: "Now expressing the same thing in two different ways, with or without & is confusing, so I think one needs to think about if old syntax should be deprecated in 8.0" would be a massive BC breakThat wasn’t in Rowans suggestion, it was in Björn’s response to the original message. You’re either not reading who wrote what before you reply, or you’re deliberately trying to imply a person has advocated for something they never even mentioned.
Even *if* the consensus was to drop support for & references in php8 - thats a major new version, with AFAIK, literally no planned ETA, of any kindbesides that's not the topic at all and i just responded to "If you point is pass-by-reference is bad and stupid, then it's off-topic and I suggest you should create a new RFC to abandon this feature" however, "that's a major new version" is completly irrelevant in this point of time - what is relevant to think about the outcome of whatever is suggested *long before* something is even seriously considered to make things right - with the least possible BC break unless it is justified by a major benefit which makes the break worth that's somehow learning from past mistakes and avoid to repeat them in similar changes - if such discussions would have happened always before consider implementations we would not sit here with similar functions but reverse parameter order and other such "nice" things which are ugly but fix them now would introduce a lot of more troubles than it solves