-
Notifications
You must be signed in to change notification settings - Fork 576
Misuse of "quote" in place of "escape" in documentation #15221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From the.rob.dixon@gmail.comThis is a bug report for perl from the.rob.dixon@gmail.com, This issue came to light with regard to this Stack Overflow solution http://stackoverflow.com/a/35918358/622310 The specific context id the perlre POD, but there may well be other I submit that using "quoting" when you mean "escaping" is a useless The OP who wrote the item referenced above claimed that the two are But the narrative in `perlre` could be much improved, especially because it All of the following references refer to v5.22.1 of perlre.pod, and I think Line 553 Line 686 Line 687 Line 1021 Lines 1027 .. 1030 Line 1039 Flags: Site configuration information for perl 5.22.1: Configured by strawberry-perl at Mon Dec 14 22:59:01 2015. Summary of my perl5 (revision 5 version 22 subversion 1) configuration: Platform: @INC for perl 5.22.1: Environment for perl 5.22.1: PATH=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program |
From @demerphqFWIW, ++ on this bug. On 10 March 2016 at 16:53, Rob Dixon <perlbug-followup@perl.org> wrote:
-- |
The RT System itself - Status changed from 'new' to 'open' |
From @tonycoz
"quote" semms to me to be the correct terminology. We quote text to avoid any special meaning for that text, eg: $x = exit; vs $x = "exit" Emacs uses the quote-next operator to insert the next character typed literally. Tony |
From @jkeenanOn Tue Mar 15 17:24:58 2016, tonyc wrote:
Tony, that suggests to me that you do not favor any documentation changes here. If so, can we close this ticket?
Thank you very much. -- |
From @demerphqOn 21 April 2016 at 03:42, James E Keenan via RT
I am not Tony, but I do not think we should close this.
I think the use of quote like this is archaic and confusing. In modern computing (and perl) terms IMO... "to quote something" means "to place some marker around arbitrary "to escape something" normally means "to prefix something such that it The key point here is that quoting normally involves a balanced Further supporting the view that escaping and quoting something are So I am rather firmly in favour of the changes the OP requested. Yves |
Fixes Perl#15221 The documentation and comments was misleading about conflating quoting a metacharacter and escaping it. Since \Q stands for quote, we have to continue to use that terminology. This commit clarifies that the two terms are often equivalent.
Fixes Perl#15221 The documentation and comments was misleading about conflating quoting a metacharacter and escaping it. Since \Q stands for quote, we have to continue to use that terminology. This commit clarifies that the two terms are often equivalent.
Fixes Perl#15221 The documentation and comments was misleading about conflating quoting a metacharacter and escaping it. Since \Q stands for quote, we have to continue to use that terminology. This commit clarifies that the two terms are often equivalent.
Fixes Perl#15221 The documentation and comments were misleading about conflating quoting a metacharacter and escaping it. Since \Q stands for quote, we have to continue to use that terminology. This commit clarifies that the two terms are often equivalent. This also adds a note that quotemeta isn't affected by locale.
Migrated from rt.perl.org#127687 (status was 'open')
Searchable as RT127687$
The text was updated successfully, but these errors were encountered: