Bug #81635 [Com]: No example of complex interpolation syntax with filenames

Edit report at https://bugs.php.net/bug.php?id=81635&edit=1 ID: 81635 Comment by: shealavington at gmail dot com Reported by: shealavington at gmail dot com Summary: No example of complex interpolation syntax with filenames Status: Closed Type: Bug Package: Scripting Engine problem Operating System: Windows 10 PHP Version: 8.0.12 Assigned To: cmb Block user comment: N Private report: N New Comment: Regarding the comment from the docs, it states specifically in single-quoted strings. I am doing this in a double-quoted string. I'm not sure if that poses an issue or just a documentation change. | As in single-quoted strings, escaping any other character will result in the backslash being printed too. In reference to escaping file paths, I completely agree they should be, however, due to legacy systems in place, I'm trying to not modify too much of the original code. Previous Comments: ------------------------------------------------------------------------ [2021-11-18 14:18:33] git@php.net Automatic comment on behalf of cmb69 Revision: https://github.com/php/doc-en/commit/59244d9ae93cc5059a07c7eadf36b02a1704512c Log: Fix #81635: No example of complex interpolation syntax with filenames ------------------------------------------------------------------------ [2021-11-18 13:55:32] cmb@php.net Nah, there is nothing special about \{[1]: | As in single quoted strings, escaping any other character will | result in the backslash being printed too. Still, it makes sense to add an example, since backslashes in filenames and the given use-case are common on Windows. [1] <https://www.php.net/manual/en/language.types.string.php#language.types.string.syntax.double> ------------------------------------------------------------------------ [2021-11-18 13:37:43] cmb@php.net Thanks for the further clarification! > $newFoo = "(FILENAME='C:\folder\{$var}.txt')" You really should escape the backslashes in the first place; then you get the desired output: <https://3v4l.org/EKFq2>. > As you mentioned, \{ should not be escaping, but does. Indeed: <https://3v4l.org/lLZqF>. That needs to be fixed in the docs. ------------------------------------------------------------------------ [2021-11-18 11:56:21] shealavington at gmail dot com Indeed unclear, and most confusing. I'm working with a filesystem path within a larger string. I need to insert my variable after a backslash. For simplicity, we're using curly braces around all of our variables used within the string, and this situation doesn't allow us to do so. ``` $foo = 'bar'; $newFoo = "(FILENAME='C:\folder\{$var}.txt')" ``` outputs a string with a now invalid file path due to the parsing inconsistency. ``` (FILENAME='C:\folder\{bar}.txt') ``` As you mentioned, \{ should not be escaping, but does. Hopefully this issue can be looked into being fixed for later versions. ------------------------------------------------------------------------ [2021-11-18 11:40:49] cmb@php.net Yeah, this is actually unclear. "hello\{$foo}" This looks like complex string interpolation syntax, but is apparently parsed as simple string interpolation syntax, so $foo is being replaced with its value. So, I assume, that the backslash acts as escape for the open *and* the closing curly braces. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=81635 -- Edit this bug report at https://bugs.php.net/bug.php?id=81635&edit=1