<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://3469/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 2, 2012, at 10:36 AM, Iestyn Bleasdale-Shepherd <<a href="mailto:iestyn@valvesoftware.com">iestyn@valvesoftware.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font face="Calibri" size="2"><span style="font-size: 11pt; "><div>Hi,</div><div> </div><div>It appears that the 'display' names produced by clang_getCursorDisplayName are not specific enough for function template specializations; that is, the template parameters reduce to '<>'. The display names of all specializations of a given function template are identical and thus ambiguous.</div></span></font></div></blockquote><div><br></div><div>That does not seem right, please file a bug.</div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font face="Calibri" size="2"><span style="font-size: 11pt; "><div> </div><div>The same problem occurs for class methods, however the display names of template class specializations are correct. The display name for an unspecialized template class is still not ideal though; for example "template <class T> class myclass" yields the display name "myclass<T>" which does not make it clear whether 'T' is a generic typename or a specific type named 'T'! In this case, "myclass<typename T>" might be better.</div></span></font></div></blockquote><div><br></div><div>Not sure about that, the display name is only to provide a user-friendly string, it's not supposed to provide unique and unambiguous identifiers.</div><div>I can see benefits either way, e.g. the shorter "myclass<T>" looks better to me, adding 'typename' to each parameter will make the display name a bit too long and unwieldy.</div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font face="Calibri" size="2"><span style="font-size: 11pt; "><div> </div><div>I thought I’d post here before submitting the above as a bug, in case I’m missing something.</div><div> </div><div>Thanks!</div><div> </div><div>iestyn Bleasdale-Shepherd</div><div> </div></span></font>_______________________________________________<br>cfe-dev mailing list<br><a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br></div></blockquote></div><br></body></html>