alexfh added inline comments.
================ Comment at: include/clang/Analysis/AnalysisDeclContext.h:424 /// methods during the analysis. - BodyFarm *BdyFrm = nullptr; + std::unique_ptr<BodyFarm> BdyFrm; ---------------- george.karpenkov wrote: > alexfh wrote: > > BdyFrm is somewhat cryptic. Maybe Farm, Bodies or something else that is > > not so weirdly abbreviated? > But that's just forced on us by the naming convention, isn't it? I think > other names are worse though: they don't tell us which class we can look at > to figure out what is it doing. LLVM Coding Standards doesn't endorse this kind of an abbreviation, on the opposite: "We cannot stress enough how important it is to use descriptive names. ... Avoid abbreviations unless they are well known." (http://llvm.org/docs/CodingStandards.html#name-types-functions-variables-and-enumerators-properly). Neither "Bdy" nor "Frm" are well known or otherwise clear to the reader. "Frm" could also stand for "Form" or "Frame", but in these cases it would also be confusing. If you consider shorter names ("Bodies" or "Farm") non-informative, we can go the other direction, e.g. "FunctionBodyFarm". Repository: rL LLVM https://reviews.llvm.org/D39220 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
