<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="">There is some movement towards making the DMD frontend available as a library, which is great. A few pull request for this have already been merged. With this in mind I thought it would be a good idea to cleanup and standardize some of the symbol names in the source code. I’m mostly thinking about making sure that the standard D naming conventions are followed, i.e. isscope -> isScope. Local variables would not need to be included (unless we want to) since those are not part of the API. I would recommend including parameter names, even though that is not part of the API, it would still show up in any generated documentation.<div class=""><br class=""></div><div class="">I think we should take the opportunity to do this before we get any more users. As far as I know there are only two users: LDC and GDC. If we wait with this for later it will make it more complicated if we have a stable API to maintain backwards compatibility with.</div><div class=""><br class=""></div><div class="">Just to be clear, I’m willing to do pull requests for this.</div><div class=""><br class=""></div><div class="">Thoughts?<br class=""><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: 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-size-adjust: auto; -webkit-text-stroke-width: 0px;">-- <br class="">/Jacob Carlborg</div>
</div>
<br class=""></div></div></body></html>