|WikiProject Computing||(Rated Start-class)|
I think that the "raw quoting" mechanism attributed to Python might have prior art in Perl, as in the q%string% style of quoting. Ccreitz 01:55, 14 June 2006 (UTC)
Too much Python?
Quote (under section "Prefixes"):
"For example, in Python 'raw strings' are preceded by an
R – compare
r"C:\Windows\". Python 2 also distinguishes two types of strings: 8-bit ASCII ("bytes") strings (the default), explicitly indicated with a
B prefix, and Unicode strings, indicated with a
So is this article a Python reference? The second sentence IMO should be omitted, or at least placed in a different section stating some languages distinguish between ASCII and Unicode strings, and then providing an example. However, the way it is currently stated is not good. 22.214.171.124 (talk) 07:58, 30 June 2013 (UTC)
- Immediately the problem arises: how do you include quotation marks themselves in the strings? If the language allows the use of both styles of quotation marks (e.g. Modula-2), then you can embed one style by quoting with the other style:
Is anyone else sick of this folksy tutorial writing in Wikipedia? The second-person voice is particularly absurd. This is an encyclopedia, not a guide on anything.
draft to improve tone and npov
todo items still in wiki code drefty.mac 07:20, 27 October 2006 (UTC)
Under the Variable interpolation section I could not get the perl code to work. Here is my log
homebox:~ jpben$ cat testr.pl
$sName = "Nancy";
$sGreet = "Hello World";
print r'$sName said $sGreet to the crowd of people.';
homebox:~ jpben$ perl testr.pl
Bad name after r' at testr.pl line 4.
homebox:~ jpben$ perl -v |head -n2
This is perl, v5.8.6 built for darwin-thread-multi-2level
I know in perl you dont need the r, since single quotes do not do variable interpolation. Perhaps this r is a mistake?
- There is no r in the perl example. You may be referring to the "raw string" example, which is not perl, and is not a feature of perl for the reason you specified. dr.ef.tymac 02:21, 20 November 2006 (UTC)
Double-up and Triple-up escape sequence
To me, Double-up and Triple-up escape sequences are completely different concepts which should not share the same headline; triple delimiters are no escape sequences at all but an extension to the dual quoting style. --TobiasHerp 12:49, 10 April 2007 (UTC)
- Good point. The article has been changed. dr.ef.tymac 15:35, 10 April 2007 (UTC)
The string presented:
"I said, \x22Can you hear me?\x22"
Suggests a 'C' language example, where the \xhh sequence would be a hexadecimal value (0x22 = ASCII double quote (") character).
If so, it appears to be flawed. My compiler (GNU's gcc) complains "warning: hex escape sequence out of range". My reference on the topic (K&R's C Programming Lange Ed. 2) is vague, but suggests that \xhh continues for any number of hex chars (0~9, a~f, A~F) so the "Ca" of "\x22Can" is included by the compiler, as well.
I voice the issue here because it was precisely this point I sought to resolve when I read the page. So I can't claim to know it requires 'correction'. Especially since it doesn't claim to be 'C' syntax. And yet it was confusing... Stubya (talk) 15:53, 29 May 2010 (UTC)
- This could be clarified, but you are correct in emphasizing that this example is not identified as 'C' syntax. There are multiple programming languages besides C where this example actually produces the intended output, even though it does not when using 'C'. It may be worth clarifying the article. dr.ef.tymac (talk) 21:33, 27 May 2010 (UTC)
FreeBASIC is a BASIC dialect that supports C-style escapes, however, you must prefix each string literal with an !, e.g.:
Would print exactly "Hello\nWorld", however,