<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: 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;" class=""><div class=""><div class="">This discussion of acronyms does raise a different issue, though. I would suggest expanding the “Avoid abbreviations” section of the API Design Guidelines a bit to make a clear distinction between truncating words just to shorten identifiers (bad) and using common acronyms (good). You don’t want people thinking they’re being advised to do this:</div><div class=""><br class=""></div><div class="">var hyperTextMarkupLanguageElement = HyperTextMarkupLanguageElement()</div></div></div></div></blockquote></div><br class=""><div class="">Sorry, I think my over-the-top example completely undermined the point I was trying to make. “HTML” and other common acronyms are clearly not being discouraged in the current guideline. But there is no acronym so obscure it can’t easily be found on the internet. So what abbreviations are you discouraging? Truncations like Str or Len? Or is this guideline really just about acronyms and not making up your own? I just thought it could be more clear.</div><div class=""><br class=""></div><div class="">—CK</div></body></html>