Anonymous user
Talk:Brace expansion: Difference between revisions
→Task is ready for accepting solutions!: clarifications
(→Task is ready for accepting solutions!: clarifications) |
|||
Line 10:
:::: Well, I'm not really with the python culture, but that's not important. I can see why the spec is setup this way, but the fact remains that the rule about unmatched bracers is underdefined. The spec should say which bracers would be considered extra for consistency across implementations. I'll withdraw the python code for now since it does fail to follow other rules, while the task hopefully can get some clarification. --[[User:Ledrug|Ledrug]] ([[User talk:Ledrug|talk]]) 03:19, 26 January 2014 (UTC)
:::: Another thing, what's supposed to happen when the string ends with an extra "\"? --[[User:Ledrug|Ledrug]] ([[User talk:Ledrug|talk]]) 03:29, 26 January 2014 (UTC)
:::::I've attempted to clarify what to do in the case of ambiguity; in general, the closest brace that makes sense in context is used. I suppose a backslash at the end of the string should just be taken as a literal. --[[User:TimToady|TimToady]] ([[User talk:TimToady|talk]]) 04:00, 26 January 2014 (UTC)
| |||