<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Mar 4, 2014, at 10:48 PM, Duncan Exon Smith <<a href="mailto:dexonsmith@apple.com">dexonsmith@apple.com</a>> wrote:<br><div><blockquote type="cite"><div dir="auto"><blockquote type="cite"><div><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite"><br><blockquote type="cite">Related, should we require use of 'override' when methods override a base<br>class method?<br></blockquote><br>My vote: require override.<br></blockquote><br>+1: override is useful and prevents errors.<br></div></blockquote>Would it be too much to have clang emit a warning/error if override is missing? I know that sounds crazy and people hate errors which fire too often, but there’s not too much C++11 code out there yet, and so we have a chance to put errors/warnings in now without too much pain. People might just get used to them and think its how code has to be written :)<br></div></blockquote><div><br></div><div>Might be a nightmare when including legacy headers, but warnings can always be disabled...</div></div></blockquote></div><br><div>A clang warning for this would be awesome, but it should be off by default. That said, the build of LLVM itself could detect that Clang had this warning and turn it on. I think it would be great to have the makefiles/cmake detect modern clang's and turn on additional warnings that we can't inflict on the world by default.</div><div><br></div><div>-Chris</div></body></html>