<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 5/27/2013 11:51 AM, Haoyi Li wrote:<br>
</div>
<blockquote
cite="mid:CALruUQKhCNuN-_O2bgtgMiXxOe9QPtRyLt3V+NYe-JxeBrO70A@mail.gmail.com"
type="cite">
<div style="">If-if-if all that works out, you would be able to <i>completely
remove </i>the<i> (</i><span
style="font-family:arial,sans-serif;font-size:13px">"b" | "B"
| "br" | "Br" | "bR" | "BR" | "rb" | "rB" | "Rb" | "RB" | </span><span
style="font-family:arial,sans-serif;font-size:13px">"r" | "u"
| "R" | "U") from the grammar specification! Not add more to
it, remove it! Shifting the specification of all the different
string prefixes into a user-land library. I'd say that's a
pretty creative way of getting rid of that nasty blob of
grammar =D.</span></div>
<div style=""><span
style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
</blockquote>
<br>
In order to achieve this ideal, and assuming you'd be keeping
backward compatibility (!), you'd have to explain how to support
both of these strings:<br>
<br>
"Hello\n"<br>
r"Hello\n"<br>
<br>
Implicit in your idea is that the plain literal creates a string of
some kind, and but the r-prefixed string would apply some user-land
function to the string. But there is no function you can apply to
string literals to make them be raw. The r prefix suppresses
interpretation that happens in un-prefixed strings. By the time a
user-land function got hold of the string, the interpretation has
already been done, information has already been lost.<br>
<br>
--Ned.<br>
</body>
</html>