<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On May 30, 2013, at 3:42, Haoyi Li <<a href="mailto:haoyi.sg@gmail.com">haoyi.sg@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div dir="ltr">
<div style=""><span style="font-family: arial, sans-serif; font-size: 13px; ">> </span><span style="font-family: arial, sans-serif; font-size: 13px; ">But still, it's amazing how C++11-ish this discussion is getting. Which may be a good hint that (as you suggest) this feature isn't a good fit for Python.</span></div>
<div style=""><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style=""><span style="font-family:arial,sans-serif;font-size:13px">I don't agree with this; while C++ is huge and terrible, C++11 actually has some pretty good stuff (e.g. real lambdas, with real closures and real lexical scoping! </span><span style="font-family:arial,sans-serif;font-size:13px">u"unicode" and r"raw" strings!</span><span style="font-family:arial,sans-serif;font-size:13px">). Dismissing something as bad just because it's something C++11 has is a terrible idea and immediately shuts out a whole range of interesting possibilities.</span></div></div></blockquote><div><br></div><div>C++11 is a set of very clever, and often very nice, improvements, but nearly all of the improvements are solutions to problems unique to C++90.</div><div><br></div><div>And if you step back, the problem most people are trying to solve here is that they don't want to do string processing inline within a function because they're worried about performance. <span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">(Of course the OP wasn't even worried about that; he just wanted to save a few keystrokes making decimals. But most of the follow ups haven't been about that.) I'd</span> guess that 90% of the time those performance worries are misguided, and the remaining 10% can already be solved by moving the strings to module level, caching the results, etc. So, we're looking for syntactic sugar for a way to accomplish one of those solutions more nicely. That's a very different problem than making strings (and other types) accessible to a compile-time metalanguage that's radically different from the runtime language, which is what C++ was solving.</div><div><br></div><div>(PS, you misattributed most of your quotes to me instead of Eric Snow. But I'm sure he'll still see then.)</div></body></html>