<div dir="ltr">Well... I think that there is nothing wrong with the current directives *and* attribute names being lowercase (with some exceptions for attributes when relating to Objective-C/Cocoa support).<div><br></div><div>One of the things I dislike in Java is the @Override. First the `override` should no be an attribute, but since it is, `@override` would be much more pleasant.</div><div><br></div><div>The same goes for directives that is what is being discussed here. I vote for lowercase.<div><br></div><div>-Van</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 25, 2016 at 5:31 PM, Антон Жилин <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Exceptions from guidelines probably can happen, given an argumentation. In attributes, @NS- and @IB- things for compatibility with Objective-C. Here, #elseif for analogy with "else if" in usual Swift. #elseIf also feels odd to me.<div>Can #end be a better name for #endif?<br><div>Anyway, I think I won't create a proposal draft until the proposals containing mentioned directives get accepted.</div></div>
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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>
<br></blockquote></div><br></div>