Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126769
Feedback-ID: id5114917:Fastmail
Message-ID: <5ffd5a1a-6632-48ab-afe9-afc84d5ccc74@rwec.co.uk>
Date: Fri, 14 Mar 2025 21:48:36 +0000
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] RFC: short and inner classes
To: internals@lists.php.net
References: <aae32397-0567-417f-adbe-6b663d5c49ae@app.fastmail.com>
 <CAPyj-LAz=3yX7mCYOijw2irrubgs2b3Piqy42_jpkek5ctKkWA@mail.gmail.com>
 <AM8P250MB0170E8274E56E96B4962578BE2D32@AM8P250MB0170.EURP250.PROD.OUTLOOK.COM>
 <CAPyj-LBB6VsF6u2X_=SHpgv-UYPAjX4tKgDgZrEE+QtTwfz+_w@mail.gmail.com>
 <cd217c68-987f-4a98-a4bd-6e075810a619@app.fastmail.com>
 <5aedb962-dfab-41ec-86ac-811dfe1074be@rwec.co.uk>
 <487b028c-20bd-4ebd-ab8f-972d9e633050@scriptfusion.com>
Content-Language: en-GB
In-Reply-To: <487b028c-20bd-4ebd-ab8f-972d9e633050@scriptfusion.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 14/03/2025 21:18, Bilge wrote:
> Just because some (incompetent) developers cannot grasp proper 
> escaping should have no bearing whatsoever on language design.


The main problem is not "grasping" it, it's the inconvenience of having 
to do it at all, and the "ugliness" (subjective, obviously) of the 
resulting code.


Backslash is used as an escape in so many different syntaxes that it's 
not uncommon to be nesting two of them inside each other, e.g. Markdown 
inside JSON:

{ "markdown": "The inner class is called 
MyNamespace\\\\MyClass\\\\\\\\InnerClass" }

The quadrupled namespace separator is still just about readable, but 
could you tell me at a glance if I have the right number of backslashes 
for the proposed inner class separator?


If we can't use "::", I'm confident we can find one that's more 
convenient to use than double-backslash.


-- 
Rowan Tommins
[IMSoP]