Nice! With that explanation, I too am -1 on another way of doing the same thing.<br><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 29, 2016 at 15:53 Magnus Ahltorp via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> 29 Aug. 2016 22:16 DifferentApps info <<a href="mailto:andre_ponzo@differentapps.com" target="_blank">andre_ponzo@differentapps.com</a>> wrote:<br>
><br>
> The advantage is that you do not need to define a conditional flag for the #if.<br>
<br>
The good news is, you don't.<br>
<br>
#if false<br>
print("Disabled code")<br>
#endif<br>
<br>
which is a time-tested way of writing C code (using #if 0).<br>
<br>
>From the Swift changelog, where they even call it an idiom of C:<br>
<br>
2014-04-30<br>
[…]<br>
* You can now use the `true` and `false` constants in build configurations,<br>
allowing you to emulate the C idioms of `#if 0` (but spelled `#if false`).<br>
<br>
One pattern I use all the time, both in C and in Swift, is this:<br>
<br>
#if false<br>
<experimental code><br>
#else<br>
<old code><br>
#endif<br>
<br>
which makes it possible to switch between the implementations quickly, something you cannot do with the proposed syntax.<br>
<br>
> Code disabling (with /{...}/) is a tool useful when developing algorithm, and disabled code should not be aimed to remain definitively in a Swift file.<br>
<br>
Which is in no way dependent on if you use the proposed syntax, traditional comments, or conditional compilation.<br>
<br>
/Magnus<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>