[llvm-dev] RFC: changing variable naming rules in LLVM codebase (original) (raw)
Chris Lattner via llvm-dev llvm-dev at lists.llvm.org
Wed Feb 27 13:58:06 PST 2019
- Previous message: [llvm-dev] RFC: changing variable naming rules in LLVM codebase
- Next message: [llvm-dev] RFC: changing variable naming rules in LLVM codebase
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 22, 2019, at 11:40 AM, David Greene <dag at cray.com> wrote:
- Local variables and formal parameters should be lowercase, with one exception: Variables/parameters that have lambda/function type should follow the function-name spelling rules. "lowercase" is a pretty drastic change from CamelCase and camelCase. So far the only argument for it I've seen is, "lldb uses it all over the place." Having one subproject drive the standard for everything else seems backward. It's certainly possible I missed other opinions on this though.
FWIW, I agree. LLDB has always been a vast outlier from the rest of the LLVM project, owing to the project origins (which aren’t relevant to the discussions at hand). I don’t think that its conventions should be highly prioritized unless they are obviously and objectively better.
In this case, the different between variable_names and TypeNames seems completely indefensible.
-Chris
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190227/a85cf1c4/attachment.html>
- Previous message: [llvm-dev] RFC: changing variable naming rules in LLVM codebase
- Next message: [llvm-dev] RFC: changing variable naming rules in LLVM codebase
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]